Availability zone database record mismatch with nova show command output

[Anton Rodionov]

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://bugs.launchpad.net/nova/+bug/1378904.

MOS 9.2 + code from stable branch from June 2017

[Andrey Volkov (avolkov)]

Anton,
Please provide api/cli you issued and sql requests as well, thanks.

[Anton Rodionov (arodionov)]

Andrey, I have attached the requested information.

[Denis Meltsaykin (dmeltsaykin)]

The corresponding upstream bug has been recently closed as Won't Fix - https://bugs.launchpad.net/nova/+bug/1378904/comments/10. Unfortunately the proposed fix is not safe enough to be backported into the stable branch and it goes against OpenStack idea to prohibit AZ renaming totally. For the above reasons I'm closing this bug as Won't Fix.

[Andrey Volkov (avolkov)]

https://review.openstack.org/#/c/509206/

[Alexander Rubtsov (arubtsov)]

Setting status to "In progress" for 9.x as a proposed fix is on code review:
https://review.fuel-infra.org/#/c/36842/

[Denis Meltsaykin (dmeltsaykin)]

The change 36842 is being reverted: https://review.fuel-infra.org/#/c/37299/

[Denis Meltsaykin (dmeltsaykin)]

The revert is merged, setting the status as Won't Fix.