AvailabilityZoneFilter returns a wrong result because of the availablity_zone in the instances table has not be updated
Bug #1677097 reported by
zengrui
This bug report is a duplicate of:
Bug #1771860: instance.availability_zone reports wrong az after live migration.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Medium
|
wind |
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 AvailabilityZon
tags: | added: availability-zones |
tags: | added: scheduler |
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in nova: | |
assignee: | nobody → wind (better) |
To post a comment you must log in.
Could you please provide the steps you have used to reproduce this, it helps to understand better and also helps to reproduce the issue.