[Bug 871966] Re: FQDN written to /etc/hosts causes problems for clustering systems

[Clint Byrum]

Excerpts from Scott Moser's message of Tue Oct 11 16:57:27 UTC 2011:
> On Tue, 11 Oct 2011, Clint Byrum wrote:
> 
> > Excerpts from Scott Moser's message of Tue Oct 11 00:18:27 UTC 2011:
> > > gethostbyname(hostname) is non-determinable.
> > > there could be multiple responses.  and indeterminable order.
> > >
> >
> > Agreed, which is precisely why I believe cloud-init must leave the FQDN
> > out of /etc/hosts if there is any response to this call.
> 
> That doesn't make any sense.  Its non-determinable, its non-determinable
> when cloud-init runs as well as later on.
> When cloud-init ran to decide if there was a response to this call, it may
> give a single value, or may give 4 values, or may give no response.  That
> may change later on when some other utility was asking.
> 

The number and content of responses is irrelevant, only that the count
of positive responses is at least one.

The idea isn't to cover the case for all time, its to cover the case
where users have not asked to have fqdn "fixed", yet we need to make a
best effort attempt to make sure it is resolvable during bootup.

If it can be resolved through the normal means, what reason do we have
to override that with a value like 127.0.1.1?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/871966

Title:
  FQDN written to /etc/hosts causes problems for clustering systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/871966/+subscriptions