3c0eadae0b
After this patch nova rejects the add host to aggregate API action if the host has instances and the new aggregate for the host would mean that these instances need to move from one AZ (even from the default one) to another. Such AZ change is not implemented in nova and currently leads to stuck instances. Similarly nova will reject remove host from aggregate API action if the host has instances and the aggregate removal would mean that the instances need to change AZ. Depends-On: https://review.opendev.org/c/openstack/tempest/+/821732 Change-Id: I19c4c6d34aa2cc1f32d81e8c1a52762fa3a18580 Closes-Bug: #1907775
13 lines
465 B
YAML
13 lines
465 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Nova now ensures that an instance cannot move between availability zones
|
|
when the host of the instance is added or removed to an aggregate that is
|
|
part of another availability zone. Moving from or to the default
|
|
availability zone is also rejected.
|
|
|
|
This resolves `bug 1907775`_ where after such move the instance become
|
|
stuck in between availability zones.
|
|
|
|
.. _bug 1907775: https://bugs.launchpad.net/nova/+bug/1907775
|