Bug 1030367

Summary:	[race] Host stays in "Preparing for maintenance" forever if requested while incoming live migrations
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-engine	Assignee:	Roy Golan <rgolan>
Status:	CLOSED ERRATA	QA Contact:	Artyom <alukiano>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.1.4	CC:	acathrow, bazulay, iheim, jentrena, jkt, lbopf, lpeer, lyarwood, mavital, michal.skrivanek, ofrenkel, pstehlik, rgolan, Rhev-m-bugs, sputhenp, yeylon
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.3.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	is35	Doc Type:	Bug Fix
Doc Text:	Previously, attempting to move a host into maintenance mode resulted in a static "Preparing for maintenance" status because virtual machines on that host with a "Migrating to" status were unable to be migrated elsewhere. Now, ongoing migrations to the chosen host are cancelled when maintenance mode is selected on that host, and the host will reattempt to enter maintenance mode after a period of five minutes.	Story Points:	---
Clone Of:	966503	Environment:
Last Closed:	2014-04-09 17:53:13 UTC	Type:	---
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:	966503
Bug Blocks:

Comment 2 Itamar Heim 2014-02-23 09:15:45 UTC

Description of problem:
Customer requests a host to enter maintenance mode while incoming live migrations are running.
Host fails to enter maintenance mode and stays in "Preparing for maintenance" even after 16 hours.

Version-Release number of selected component (if applicable):
rhevm-backend-3.1.0-53.el6ev
vdsm-4.10.2-1.13.el6ev

How reproducible:
Customer has only tried this once so far.

Steps to Reproduce:
1. Start live migrations to a host.
2. Through webadmin gui, request the host to enter maintenance mode while the incoming live migrations are running.
3.

Actual results:
Host remains in "Preparing for maintenance" forever.

Expected results:
Either:

a) Host eventually enters maintenance mode as requested.

- Incoming live migrations are cancelled.
or
- Incoming live migrations are completed and then live migrated back out of the host.

b) An error message is displayed and host remains up.
E.g. "Could not switch to maintenance mode while migrations targeting this host are running. Running migration tasks are <list of VM's currently migrating to this host>".

Comment 4 Artyom 2014-03-20 13:15:19 UTC

Verified on is35
If live migration in progress, and we put destination host to maintenance, maintenance failed(because migration in progress), but after 5 minutes engine repeat attemption and success(migrate vms on other host and put host to maintenance).

Comment 5 Zac Dover 2014-04-03 02:26:00 UTC

This bug is currently attached to errata RHBA-2014:17286. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.

* Consequence: What happens when the bug presents.

* Fix: What was done to fix the bug.

* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.

Comment 7 errata-xmlrpc 2014-04-09 17:53:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0384.html