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.
Reviewed: https:/ /review. openstack. org/643151 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=73aaead294b 9df412305abb1cb 01aac95477bcc1
Committed: https:/
Submitter: Zuul
Branch: master
commit 73aaead294b9df4 12305abb1cb01aa c95477bcc1
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
Related-Bug: #1819963