live migration force node not working with v2.67

[jayaditya gupta]

Since "Stein", by default, is not possible to "force" live-migrate an instance to a node without schedule verification.
This means that if the target node is disable the live-migration will fail.

This was introduced with:
https://github.com/openstack/nova/commit/36a91936a821b0c1f502d7d8f1ffd8c4d179d212
https://review.opendev.org/#/c/634600/

This change takes effect starting in microversion v2.68.
We can force the client to use v2.67. Using "--os-compute-api-version 2.67" but it's not working

[sean mooney (sean-k-mooney)]

it might be failing due to placment allocations
see https://bugs.launchpad.net/nova/+bug/1712008

as noted in https://github.com/openstack/nova/blob/master/releasenotes/notes/bug-1712008-4ab2538211b8c3d9.yaml

we allow the schduler to be bypassed but still requrie the placment allcoation to succeed

can you confrim if placmenet has enough resouce for the vm.

if there are not enough resouce in placment then this is not a bug.

[sean mooney (sean-k-mooney)]

by the way without the scheduler logs for the instance migration and the placment logs for the same we likely can triage this bug.

can you provide those.

this should be reproducible with a functional test too i guess.

i set this to incomplete since we dont have enough information about your deployment to know if this is really a bug.

[Launchpad Janitor (janitor)]

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]