Actually, once nova send port_update() message to notify the new host of the
port, ML2 will send update_port( to every agents.
The agent which is hosting the port will now resend
get_device_details()/update_device_up() and the port will not remain in BUILD
state.
That's the reason why I'm invalidating the bug.
The behavior described bug Mike on comment #7 will be tracked by bug
1416933
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1274160
Title:
port_update from nova could potentially occurs after
get_device_details/update_device_up
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
during live-migration, if neutron process port_update(binding:host)
after processing the rpc message get_device_details/update_device_up,
the port will remain in a BUILD state.
this is a race condition that I have never seen, but I think this
could potentially occurs, since the agent could trigger its RPC
message before neutron receives its API call.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1274160/+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
