<div dir="ltr">Thanks for the heads up. </div><br><div class="gmail_quote"><div dir="ltr">El mié., 5 oct. 2016 a las 4:50, Ihar Hrachyshka (<<a href="mailto:ihrachys@redhat.com">ihrachys@redhat.com</a>>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sergio Morales Acuña <<a href="mailto:semoac@gmail.com" class="gmail_msg" target="_blank">semoac@gmail.com</a>> wrote:<br class="gmail_msg">
<br class="gmail_msg">
> Hi.<br class="gmail_msg">
><br class="gmail_msg">
> I'm facing a problem related to dns_name and dnsmasq.<br class="gmail_msg">
><br class="gmail_msg">
> Nova and Neutron can create a port with dns_name and dnsmasq it's<br class="gmail_msg">
> correctly updating "/addn_host".<br class="gmail_msg">
><br class="gmail_msg">
> The problem is when Nova boot an instance using a new or previusly<br class="gmail_msg">
> created port. The port has the correct dns_name but dnsmaq (dhcp_agent)<br class="gmail_msg">
> it's using the generic (ex. host-10-0-0-16) names.<br class="gmail_msg">
><br class="gmail_msg">
> If I restart dhcp_agent or do a port-update on the port, the correct name<br class="gmail_msg">
> is added to addn_host.<br class="gmail_msg">
><br class="gmail_msg">
> Any ideas?<br class="gmail_msg">
> _______________________________________________<br class="gmail_msg">
> OpenStack-operators mailing list<br class="gmail_msg">
> <a href="mailto:OpenStack-operators@lists.openstack.org" class="gmail_msg" target="_blank">OpenStack-operators@lists.openstack.org</a><br class="gmail_msg">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br class="gmail_msg">
<br class="gmail_msg">
Probably a bug in Mitaka where Neutron controller does not notify DHCP<br class="gmail_msg">
agent about an update. I think it should be solved in Newton with<br class="gmail_msg">
<a href="https://review.openstack.org/#/c/355117/" rel="noreferrer" class="gmail_msg" target="_blank">https://review.openstack.org/#/c/355117/</a> and<br class="gmail_msg">
<a href="https://review.openstack.org/#/c/375189/" rel="noreferrer" class="gmail_msg" target="_blank">https://review.openstack.org/#/c/375189/</a> plus other related patches that<br class="gmail_msg">
belong to push-notifications blueprint.<br class="gmail_msg">
<br class="gmail_msg">
Note that those patches are not safe to backport back to Mitaka, so if we<br class="gmail_msg">
get a bug reported against Mitaka for the behaviour you describe, we may<br class="gmail_msg">
need to solve it in some other way.<br class="gmail_msg">
<br class="gmail_msg">
Ihar<br class="gmail_msg">
</blockquote></div>