@Kevin, here is the bug and the extra information:
https://bugs.launchpad.net/neutron/+bug/1630603/
Thanks,
El mié., 5 oct. 2016 a las 19:05, Kevin Benton ()
escribió:
> What's strange is that it's happening with a previously created port,
> which the dhcp agent should already know about even w
What's strange is that it's happening with a previously created port, which
the dhcp agent should already know about even without an update.
@Sergio,
Can you open a bug for this and provide exact steps to reproduce this?
Thanks,
Kevin Benton
On Wed, Oct 5, 2016 at 12:50 AM, Ihar Hrachyshka
wr
Thanks for the heads up.
El mié., 5 oct. 2016 a las 4:50, Ihar Hrachyshka ()
escribió:
> Sergio Morales Acuña wrote:
>
> > Hi.
> >
> > 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_hos
Sergio Morales Acuña wrote:
Hi.
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 corr
Hi.
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)
