Bug closed due to lack of activity, please feel free to reopen if
needed.
** Changed in: neutron
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1630603
Title:
internal dns is not updated correctly on nova boot
Status in neutron:
Won't Fix
Bug description:
I'm facing a problem related to dns_name and dnsmasq.
Nova and Neutron can create a port with dns_name and dnsmasq it's
correctly updating "/addn_host".
The problem is when Nova boot an instance using a new or previusly
created port. The port has the correct dns_name but dnsmaq
(dhcp_agent) it's using the generic (ex. host-10-0-0-16) names.
If I restart dhcp_agent or do a port-update on the port, the correct
name is added to addn_host.
I'm using kolla on 3 nodes, images build
source:http://tarballs.openstack.org/neutron/neutron-stable-mitaka.tar.gz (from
1 week ago) on Ubuntu 16.06.
Step-by-step reproduction steps:
Please check this out: http://paste.openstack.org/show/584464/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1630603/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
