yahoo-eng-team team mailing list archive

[Dan Smith <dms@xxxxxxxxxxxxx>]

This sounds like a JuJu problem to me :)

IMHO, /etc/hosts should not redirect $HOSTNAME to anything other than a
routable external interface in a real environment with working DNS.
Assuming your machine is not called "localhost" I think that this is a
configuration issue.

** Changed in: nova
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1201873

Title:
  dnsmasq does not use -h, so /etc/hosts sends folks to loopback when
  they look up the machine it's running on

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
   from dnsmasq(8):

        -h, --no-hosts
                Don't read the hostnames in /etc/hosts.

  
  I reliably get bit by this during certain kinds of deployments, where my nova-network/dns host has an entry in /etc/hosts such as:

  127.0.1.1    hostname.example.com hostname

  I keep having to edit /etc/hosts on that machine to use a real IP,
  because juju gets really confused when it looks up certain openstack
  hostnames and gets sent to its own instance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1201873/+subscriptions