Public bug reported: Description =========== We are using victoria nova and find that after a same-host-cold-migrate, subsequently cold migrate could break anti-affinity policy.
Steps to reproduce ================== 1 provision a openstack cluster with 2 compute nodes 2 create a server group with anti-affinity rule 3 create two vms binding tot he server group 4 disable compute node B 5 cold migrate server on node A and confirm it 6 right after confirm succeeded, migrate server on node B 7 check vm host if not on the same host , then repeat 5 - 6 Expected result =============== servers will reside on different nodes ** Affects: nova Importance: Undecided Status: New -- 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/1999126 Title: resize to the same host unexpectedly clears host_info cache Status in OpenStack Compute (nova): New Bug description: Description =========== We are using victoria nova and find that after a same-host-cold-migrate, subsequently cold migrate could break anti-affinity policy. Steps to reproduce ================== 1 provision a openstack cluster with 2 compute nodes 2 create a server group with anti-affinity rule 3 create two vms binding tot he server group 4 disable compute node B 5 cold migrate server on node A and confirm it 6 right after confirm succeeded, migrate server on node B 7 check vm host if not on the same host , then repeat 5 - 6 Expected result =============== servers will reside on different nodes To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1999126/+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