OpenStack Compute (nova)

Volume connections and vifs are left undeleted if live migration fails

Bug #1402983 reported by zhangtralon on 2014-12-16

This bug report is a duplicate of: Bug #1437154: instance's host isn't updated if nova-compute stops operating during live-migration. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Compute (nova)	Confirmed	Undecided	zhangtralon

Bug Description

It leaves over volume link and security group rules in the destination host , if the nova-compute process of the source host interrupts after the pre_live_migration operation finishes for some reason

Tags:

zhangtralon (zhangchunlong1) on 2014-12-16

Changed in nova:
assignee:	nobody → zhangtralon (zhangchunlong1)

Lingxian Kong (kong) on 2014-12-18

summary:

- Legacy volume link and security group rules if live migration fails
+ Volume connections and vifs are left undeleted if live migration fails

Revision history for this message

Lingxian Kong (kong) wrote on 2014-12-18:

I met the same problem.

If the nova-compute process located in the source host broken down after the 'pre_live_migration' operation in the dest host, there will be some resources left there, e.g. the volume connection and the vifs, which should be deleted

Changed in nova:
status:	New → Confirmed

Pawel Koniszewski (pawel-koniszewski) on 2015-06-01

tags:

added: live-migrate

Revision history for this message

Eli Qiao (taget-9) wrote on 2015-08-19:

it seems quite similar with https://bugs.launchpad.net/nova/+bug/1437154
the instance's state is messed.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1437154 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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