neutron

why doesn't dnsmasq update metastore with hostname

Asked by Dave Johnston

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

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

Question information

Language:
English Edit question
Status:
Answered
For:
neutron Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
yong sheng gong (gongysh) said : 		#1

 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.

Can you help with this problem?

Provide an answer of your own, or ask Dave Johnston for more information if necessary.

To post a message you must log in.