nova allows to live-migrate instance from one availability zone to another

Bug #1452568 reported by Timofey Durakov on 2015-05-07
48
This bug affects 8 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Low
Unassigned

Bug Description

Nova allows to live migrate instance from one AZ to another:
Steps to reproduce:
1.boot instance with --availability-zone param
2. live migrate this instance on host located in another AZ, nova live-migration inst1 host2

If user specify host during live-migration scheduler doen't make any checks:
Result: instance migrate successfully, but information in instances table in db doesn't updates
mysql> select hostname, availability_zone from instances where deleted=false;
+----------+-------------------+
| hostname | availability_zone |
+----------+-------------------+
| demo | alice-zone |
+----------+-------------------+

while nova show command show real AZ info:
root@node-7:~# nova show demo
+--------------------------------------+--------------------------------------------------------------------------------------------------+
| Property | Value |
+--------------------------------------+--------------------------------------------------------------------------------------------------+
| OS-EXT-AZ:availability_zone | bob-zone |
| name | demo |
+--------------------------------------+--------------------------------------------------------------------------------------------------+

Nova should forbid such live migration, by adding extra checks, or update info in db table to provide data consistency

tags: added: live-migrate
tags: added: availability-zone
Changed in nova:
assignee: nobody → Sylvain Bauza (sylvain-bauza)
importance: Undecided → Low
tags: added: scheduler
Changed in nova:
status: New → Confirmed
Jason Pan (jason-p-c) wrote :

HI Sylvain,
I have a question about this bug.
In your opinion that cross availability zone live migrate is not allow?

tags: added: availability-zones
removed: availability-zone
Paul Murray (pmurray) on 2015-11-06
tags: added: live-migration
removed: live-migrate
Nan Zhang (nanzhang) on 2015-12-03
Changed in nova:
assignee: Sylvain Bauza (sylvain-bauza) → NanZhang (nanzhang)

Fix proposed to branch: master
Review: https://review.openstack.org/254041

Changed in nova:
status: Confirmed → In Progress
Changed in nova:
status: In Progress → Confirmed
assignee: Nan Zhang (nanzhang) → nobody
Mingxuan Ran (ranmx) on 2016-02-02
Changed in nova:
assignee: nobody → Mingxuan Ran (ranmx)
Mingxuan Ran (ranmx) on 2016-02-02
Changed in nova:
status: Confirmed → In Progress

Above fix does not really fix this issue, so marking as not in progress.

Changed in nova:
assignee: Mingxuan Ran (ranmx) → nobody
status: In Progress → Confirmed
stgleb (gstepanov) on 2016-03-17
Changed in nova:
assignee: nobody → stgleb (gstepanov)
stgleb (gstepanov) on 2016-03-17
Changed in nova:
assignee: stgleb (gstepanov) → nobody
stgleb (gstepanov) wrote :

I guess this patch https://review.openstack.org/254041 fixes only updating of AZ. But i didn't found any restrictions for migration instances from one AZ to another.

Prateek Arora (parora) on 2016-08-19
Changed in nova:
assignee: nobody → Prateek Arora (parora)
Sean Dague (sdague) on 2017-06-23
Changed in nova:
assignee: Prateek Arora (parora) → nobody
Sylvain Bauza (sylvain-bauza) wrote :

Closing an old bug, as it was fixed by http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/check-destination-on-migrations-newton.html

Now, if you provide a destination, we verify by calling the scheduler for that target unless you provide an explicit "force" flag to the migration call.

Changed in nova:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers