Availability zone database record mismatch with nova show command output
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Won't Fix
|
High
|
Andrey Volkov | ||
9.x |
Won't Fix
|
High
|
Andrey Volkov |
Bug Description
When a new aggregate(agg1) is created, a host is added to it and an instance is launched with new availability zone(az1),
then the nova show command output shows availability zone value as "az1" and in the nova database the availability zone value for the instance is stored as "az1"
When the host is removed from the aggregate(agg1), the nova show command output shows the availability zone as "nova" where as the database reflects the old value "az1". There is a mismatch of availability zone field value in nova show command and in the nova database.
The impact of the issue is the migration of vm fails, as the availability zone value in the nova database is not updated to new value.
Please refer to a similar bug which we have found https:/
MOS 9.2 + code from stable branch from June 2017
description: | updated |
Changed in mos: | |
importance: | Undecided → High |
Changed in mos: | |
status: | Won't Fix → Confirmed |
Changed in mos: | |
assignee: | nobody → Andrey Volkov (avolkov) |
Changed in mos: | |
status: | In Progress → Won't Fix |
milestone: | none → 10.0 |
Anton,
Please provide api/cli you issued and sql requests as well, thanks.