*** This bug is a duplicate of bug 1065440 ***
https://bugs.launchpad.net/bugs/1065440
** This bug has been marked a duplicate of bug 1065440
resize does not migrate DHCP host information
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1065516
Title:
nova migrate does not update bridge configuration on destination node
Status in OpenStack Compute (Nova):
New
Bug description:
This may be related to https://bugs.launchpad.net/nova/+bug/939060
In Essex/stable, using 'nova migrate' to migrate an instance to
another succeeds but the instance does not get a DHCP address on start
because the dnsmasq entries for the instance do not get added to the
dnsmasq config file.
To duplicate:
1) boot instance
2) on the compute node where the instance is running view the dnsmasq config
file (in this case /var/lib/nova/networks/nova-br100.conf). The MAC address is
present here.
3) run 'nova migrate' to migrate the instance.
4) on the original source compute node verify that the mac address is still
present in the config file
5) on the compute node where the instance is now running verify that the mac
address does not exist in the dnsmasq config file
As a result the instance does not get a response from the
DHCPDISCOVER.
This can be resolved by restarting nova-network on the source and
destination compute nodes and rebooting the instance.
This is present in Essex/stable - I have not verified it in newer
releases or trunk.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1065516/+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
