Change of availability zone

asked 2020-04-23 07:04:35 -0500

bjoernh gravatar image

Dear all,

we have a few instances that were created in the very beginning of our cloud deployment. After their creation, we have updated the main availability zone name from "nova" to a new name to better reflect our environment. However, these old instances are still assigned to AZ "nova" and I cannot migrate them to other compute nodes. The scheduler complains that it cannot find any candidate hosts given the non-existing AZ name. I have already tried to change the AZ for these few instances in the nova.instances table directly. However, the scheduler still thinks it should schedule to AZ "nova". What can I do to convince it that these instances are now in the new AZ?

Thank you and best regards, Björn

edit retag flag offensive close merge delete