Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1168676

Summary:	nova evacuate fails when done twice for an instance
Product:	Red Hat OpenStack	Reporter:	Marko Myllynen <myllynen>
Component:	openstack-nova	Assignee:	Eoghan Glynn <eglynn>
Status:	CLOSED NEXTRELEASE	QA Contact:	nlevinki <nlevinki>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 7)	CC:	berrange, dasmith, eglynn, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone:	z5	Keywords:	ZStream
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-05 17:00:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1179934
Bug Blocks:

Description Marko Myllynen 2014-11-27 14:57:37 UTC

Description of problem:
When doing nova evacuate for a volume backed (Cinder/LVM) instance it works ok for the first time but the second evacuation fails for the instance.

Version-Release number of selected component (if applicable):
openstack-nova-common-2014.1.3-4.el7ost.noarch

How reproducible:
Always

Steps to Reproduce:
1. Boot up a volume backed instance on hostA
2. Once the instance is up, wait a moment and poweroff hostA
3. nova evacuate <id> hostB
4. Once the instance is up, wait a moment and poweroff hostB
3. nova evacuate <id> hostC

Actual results:
Instance has Error Status, NoState Power State.

Expected results:
Instance running on hostC.

Additional info:
nova stop <id> / nova start <id> nor resetting its state does not help, the instance ends up to Error State when trying to start it thus the instance seem to have become unusable.

Comment 3 Marko Myllynen 2014-11-28 11:17:36 UTC

I'm seeing something similar with nova host-evacuate with Cinder/LVM volume backed hosts. After the first nova host-evacuate an instance is running fine on the target host but after shutting it down and host-evacuating to another host the instance never comes up again, it's stuck in rebuild / rebuild_spawning / notstate state indefinitely.

Comment 10 Pádraig Brady 2015-01-12 13:59:53 UTC

Possibly related is this upstream report on incorrect libvirt xml being generated on evacuate for instances backed by cinder/LVM: http://pad.lv/1299368

Comment 16 Stephen Gordon 2017-06-05 17:00:35 UTC

Issues still exist in this area but are tracked by other, more recent, bugs.