** Changed in: nova/kilo
Status: Fix Committed => Fix Released
--
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/1430042
Title:
Virtual Machine could not be evacuated because virtual interface
creation failed
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) kilo series:
Fix Released
Bug description:
I believe this issue is related to Question 257358
(https://answers.launchpad.net/ubuntu/+source/nova/+question/257358).
On the source host we see the successful vif plug:
2015-03-09 01:22:12.363 629 DEBUG neutron.plugins.ml2.rpc
[req-5de70341-d64b-4a3a-bc05-54eb2802f25d None] Device
14ac5edd-269f-4808-9a34-c4cc93e9ab70 up at agent ovs-agent-ipxxxxxxxxx
update_device_up /usr/lib/python2.7/site-packages/neutron/plugins/ml2/rpc.py:156
2015-03-09 01:22:12.392 629 DEBUG oslo_concurrency.lockutils
[req-5de70341-d64b-4a3a-bc05-54eb2802f25d ] Acquired semaphore "db-access" lock
/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:377
2015-03-09 01:22:12.436 629 DEBUG oslo_concurrency.lockutils
[req-5de70341-d64b-4a3a-bc05-54eb2802f25d ] Releasing semaphore "db-access"
lock /usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py:390
2015-03-09 01:22:12.437 629 DEBUG oslo_messaging._drivers.amqp
[req-5de70341-d64b-4a3a-bc05-54eb2802f25d ] UNIQUE_ID is
740634ca8c7a49418a39c429669f2f27. _add_unique_id
/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqp.py:224
2015-03-09 01:22:12.439 629 DEBUG oslo_messaging._drivers.amqp
[req-5de70341-d64b-4a3a-bc05-54eb2802f25d ] UNIQUE_ID is
3264e8d7dd7c492d9aa17d3e9892b1fc. _add_unique_id
/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqp.py:224
2015-03-09 01:22:14.436 629 DEBUG neutron.notifiers.nova [-] Sending events:
[{'status': 'completed', 'tag': u'14ac5edd-269f-4808-9a34-c4cc93e9ab70',
'name': 'network-vif-plugged', 'server_uuid':
u'2790be4a-5285-46aa-8ee2-c68f5b936c1d'}] send_events
/usr/lib/python2.7/site-packages/neutron/notifiers/nova.py:237
Later, the destination host of the evacuation attempts to plug the vif
but can't:
2015-03-09 02:15:41.441 629 DEBUG neutron.plugins.ml2.rpc
[req-5ea6625c-a60c-48fb-9264-e2a5a3ed0d26 None] Device
14ac5edd-269f-4808-9a34-c4cc93e9ab70 up at agent ovs-agent-ipxxxxxxxxxx
update_device_up /usr/lib/python2.7/site-packages/neutron/plugins/ml2/rpc.py:156
2015-03-09 02:15:41.485 629 DEBUG neutron.plugins.ml2.rpc
[req-5ea6625c-a60c-48fb-9264-e2a5a3ed0d26 None] Device
14ac5edd-269f-4808-9a34-c4cc93e9ab70 not bound to the agent host ipxxxxxxxxx
update_device_up /usr/lib/python2.7/site-packages/neutron/plugins/ml2/rpc.py:163
The cause of the problem seems to be that the neutron port does not
have is binding:host_id properly updated on evacuation, the answer to
question 257358 looks like the fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1430042/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
