yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #05650
[Bug 1198355] Re: Adding subnet after an instance has been launched on a network causes dhcp failure
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1198355
Title:
Adding subnet after an instance has been launched on a network causes
dhcp failure
Status in OpenStack Neutron (virtual network service):
Expired
Bug description:
Adding a 2nd subnet to a network on which an instance has been
launched causes dhcp failure on that network
Steps to reproduce:
1) Create a network and subnet
2) Launch instance on the network
3) Add a 2nd subnet to the network
It looks quantum is assigning addresses from the new subnet to
instances, but not adding those addresses to the dnsmasq config.
Syslog shows that dnsmasq is reporting that no addresses are available
for the instance's mac.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1198355/+subscriptions