Bug 2303395 - Live migration is failing to request non-existing availability zone name
Summary: Live migration is failing to request non-existing availability zone name
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 17.1 (Wallaby)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: OSP DFG:Compute
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-07 08:18 UTC by bporwal
Modified: 2024-10-07 17:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-10-07 17:45:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-32627 0 None None None 2024-08-21 12:24:52 UTC

Description bporwal 2024-08-07 08:18:18 UTC
Description of problem:

VM live migration failing due to non-existing Availability Zone.
Its requesting to AZ which has been renamed. 

Version-Release number of selected component (if applicable):

Red Hat OpenStack Platform release 17.1.1 (Wallaby)

How reproducible:


Steps to Reproduce:
1. Live migration is attempted by defining specific destination 
2. Live migration is attempted without defining any destination 
3. Migration enters to error with "No Valid host"

Actual results:

Unable to complete live-migration 

Expected results:

Migration should be finished successfully.

Additional info:

I will be adding into below notes.

Comment 5 smooney 2024-08-14 13:47:47 UTC
so as a starting poitn we do not support renaming aviabality zones.
we also do not support moving host between aviablity zones if they have instances and moving instance between aviablity zones is only supported
in limited cases.

i will review the bug report but the customer is starting form an unsupported state so we may not be able to provide assistance depending on the exact details.

Comment 20 smooney 2024-10-07 17:45:25 UTC
cloasing as defered with  https://bugs.launchpad.net/nova/+bug/2083858 as an upstream tracker for the bug.

based on how we fix this upstream we will determine if we can backport it and to which release.

a workaround for now is to shelve and unshelve affected instance to update the AZ in the request spec to match the new name.

as noted elsewhere az renames are not supported if there is any instance that refenced the az.

while we could not prove this form the logs we belive that the effected instances in this case where shelve when the az was renamed and
the live migration issue was a latent effect of the az rename.


Note You need to log in before you can comment on or make changes to this bug.