we shoudl discuss this more however it is perfectly valid for a resize to move a VM to a different az as long as the VM was not created with an AZ in the original request.
are not expected to align to cells and you can have multiple cells in the same az and multiple AZ in the same cell concurrently.
if an instance does not request an az in the VM create request there is no expectation that the VM should be tied to the AZ for its lifetime when migrated resize evacuated or otherwise moved.
adding schduler support for cross az attach would be a feature not a bug which is why i marked this as invalid.
setting this to invalid
we shoudl discuss this more however it is perfectly valid for a resize to move a VM to a different az as long as the VM was not created with an AZ in the original request.
are not expected to align to cells and you can have multiple cells in the same az and multiple AZ in the same cell concurrently.
if an instance does not request an az in the VM create request there is no expectation that the VM should be tied to the AZ for its lifetime when migrated resize evacuated or otherwise moved.
adding schduler support for cross az attach would be a feature not a bug which is why i marked this as invalid.
the current behaviour is expected.
the https:/ /docs.openstack .org/nova/ latest/ configuration/ config. html#DEFAULT. default_ schedule_ zone
can be used to force the vms to have an AZ when one is not requested
if that is not set and no az is provided vms are expected to be able to float across AZs