Ask Your Question
0

why doesn't dnsmasq update metastore with hostname

asked 2013-10-08 08:33:24 -0500

Hi, I have an Openstack Havana install with Neutron networking. When my instances boot, they receive an IP. If I do a nslookup on the IP I can see dnsmasq also generated a hostname.

i.e. instance with ip 10.0.0.2

nslookup 10.0.0.2

Server: 10.0.0.3 Address: 10.0.0.3#53

2.0.0.10.in-addr.arpa name = host-10-0-0-2.bfsopenstack.

Other instances can use ' host-10-0-0-2.bfsopenstack' to contact this host, but if I look in the meta-store: curl http://169.254.169.254/latest/meta-data/public-hostname (http://169.254.169.254/latest/meta-da...)

I get testmachine.novalocal

This means my machines hostname is setup in correctly as cloud-init reads from the metastore. Is this a bug, or a feature not implemented ?

Thanks

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2013-10-14 01:16:44 -0500

gongysh gravatar image

host-10-0-0-2.bfsopenstack is from neutron, testmachine.novalocal is from nova metadata. now nova does not pass neutron the vm name.

I think we can file a bug for it.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2013-10-08 08:33:24 -0500

Seen: 18 times

Last updated: Oct 14 '13