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

Bug 1670329

Summary:	Can't move host to maintenance if not active
Product:	[oVirt] ovirt-engine	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	BLL.Infra	Assignee:	Martin Perina <mperina>
Status:	CLOSED DUPLICATE	QA Contact:	Lukas Svaty <lsvaty>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	bugs
Target Milestone:	---	Flags:	rule-engine: ovirt-4.3+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-23 08:28:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2019-01-29 09:54:05 UTC

I've 2 hosts running hosted engine VM only.
One of the 2 hosts is also providing storage over NFS.
At boot this morning, the host providing storage is in failed state due to bug #1670312.
In engine (running on the other host) I see the failing one with upgrade available despite  yum update is not showing any update.
In order to fix it I tried to move the host to maintenance and I got the following message:

Operation Canceled
Error while executing action: Cannot switch Host to Maintenance mode.
Host still has running VMs on it and is in Non Responsive state.

It's true that it's in non responsive state, but it's false it has running VMs on it.

Comment 1 Martin Perina 2019-08-23 08:28:21 UTC


*** This bug has been marked as a duplicate of bug 1574443 ***