yahoo-eng-team team mailing list archive

[zengrui <1677097@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When you do a live-migration for an instance from one zone to another successfully or you change the zone of  
the compute node which the instance launched on, but the availablity_zone of this instance in the instances table won't be updated. 
Then when you do a cold_migrate or resize the instance, the AvailabilityZoneFilter will get a wrong zone of the instance, and the filter result must be wrong, and maybe you won't get the result you want for the cold_migrate or resize.

** 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/1677097

Title:
  AvailabilityZoneFilter returns a wrong result because of the
  availablity_zone in the instances table has not be updated

Status in OpenStack Compute (nova):
  New

Bug description:
  When you do a live-migration for an instance from one zone to another successfully or you change the zone of  
  the compute node which the instance launched on, but the availablity_zone of this instance in the instances table won't be updated. 
  Then when you do a cold_migrate or resize the instance, the AvailabilityZoneFilter will get a wrong zone of the instance, and the filter result must be wrong, and maybe you won't get the result you want for the cold_migrate or resize.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1677097/+subscriptions