Can't reproduce bug on our test environment due to lack of appropriate
HW. As I understand, fix was verified, so I move bug to "Fix released".
** Changed in: mos/9.x
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/1658070
Title:
Failed SR_IOV evacuation with host
Status in Mirantis OpenStack:
Confirmed
Status in Mirantis OpenStack 9.x series:
Fix Released
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) newton series:
In Progress
Status in OpenStack Compute (nova) ocata series:
Fix Committed
Bug description:
When we try evacuate SR-IOV vm on concret host the VM is in ERROR
state
Steps to reproduce:
1) Download trusty image
2) Create image
3) Create vf port:
neutron port-create <net> --binding:vnic-type direct --device_owner
nova-compute --name sriov
4) Boot vm on this port:
nova boot vm --flavor m1.small --image 1ff0759c-ea85-4909-a711-70fd6b71ad23
--nic port-id=cfc947be-1975-42f3-95bd-f261a2eccec0 --key-name vm_key
5) Sgut down node with vm
6) Evacuate vm:
nova evacuate vm node-5.test.domain.local
Expected result:
VM evacuates on the 5th node
Actual result:
VM in error state
Workaround:
We can evacuate without pointing the host just nova evacuate vm
Environment:
#785 snap
2 controllers? 2 compute with SR-IOV
To manage notifications about this bug go to:
https://bugs.launchpad.net/mos/+bug/1658070/+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
