availability_zone in request_specs not updated when live migrate vm from one availability zone to another

Bug #1861964 reported by HYSong
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Won't Fix
Undecided
HYSong

Bug Description

availability_zone in request_specs not updated when live migrate vm from one availability zone to another, and if the old aggregate's host demount, vm migration will be failed.

Steps to reproduce
==================

1) create aggregation: aggregate01 using AZ: zone01, and bonding cmp001;
2) create aggregation: aggregate02 using AZ: zone02, and bonding cmp002;
3) create flavor: test_flavor01, and set properties fit to aggregate01/aggregate02;
4) create instance: test_vm01 using test_flavor01 and --availability-zone set to zome01;
5) check OS-EXT-AZ:availability_zone using 'openstack server show test_vm01' is set to zone01, and the vm's availability_zone in request_specs is set to zone01 too.
6) live migrate test_vm01 to cmp002;
7) check OS-EXT-AZ:availability_zone using 'openstack server show test_vm01' is set to zone02, but the vm's availability_zone in request_specs is still zone01.
8) demount cmp001 on aggregate01, then bonding cmp001 to aggregate02;
9) live migrate test_vm01 without given target node will be failed. because availability_zone in request_specs is still zone01.

I think the value of availability_zone in request_specs should be updated, and the vms should use new availability_zone in request_specs when scheduling.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.opendev.org/706647

HYSong (songhongyuan)
description: updated
Changed in nova:
assignee: nobody → HYSong (songhongyuan)
status: New → In Progress
Revision history for this message
Sylvain Bauza (sylvain-bauza) wrote :

This shouldn't be accepted.
If you create an instance by asking a specific AZ, the design is that you can't migrate it to another AZ unless you force it.

When calling live-migrate by the latest API microversion, even with asking to go to a specific host, Nova wouldn't accept it.

See https://docs.openstack.org/nova/latest/admin/availability-zones.html#implications-for-moving-servers for knowing more about the design.

Closing this bug.

Changed in nova:
status: In Progress → Invalid
status: Invalid → Won't Fix
Revision history for this message
norman shen (jshen28) wrote :

Hi, I think it would be good to allow rename availability zones. I agree allow migrate across different az is pretty anti intuition, but since deployments are changing all the time, sometimes az has to be renamed or modified to reflect changes.

Advice for these situations are appreciated..

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.