When resizing a server that was not created in an explicit
zone, the scheduler can pick a host in another zone and
conductor will update the instance.availability_zone value
for the new dest host zone.
The problem is when reverting the resize, the server goes
back to the original source host/zone but the
instance.availability_zone value in the database is not
updated which can lead to incorrect results when listing
servers and filtering by zone.
This adds a functional recreate test for the bug.
Change-Id: Ib107650d6a2c991c26b646a0dd10ddc7a3fb7e56
Related-Bug: #1819963
(cherry picked from commit 73aaead294b9df412305abb1cb01aac95477bcc1)
Reviewed: https:/ /review. openstack. org/648401 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=0b2345442df c99586c1e2b5ca1 3c54fe8045e5c8
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit 0b2345442dfc995 86c1e2b5ca13c54 fe8045e5c8
Author: Matt Riedemann <email address hidden>
Date: Wed Mar 13 15:53:09 2019 -0400
Add functional recreate test for bug 1819963
When resizing a server that was not created in an explicit availability_ zone value
zone, the scheduler can pick a host in another zone and
conductor will update the instance.
for the new dest host zone.
The problem is when reverting the resize, the server goes availability_ zone value in the database is not
back to the original source host/zone but the
instance.
updated which can lead to incorrect results when listing
servers and filtering by zone.
This adds a functional recreate test for the bug.
Change-Id: Ib107650d6a2c99 1c26b646a0dd10d dc7a3fb7e56 12305abb1cb01aa c95477bcc1)
Related-Bug: #1819963
(cherry picked from commit 73aaead294b9df4