Bug 1670329 - Can't move host to maintenance if not active
Summary: Can't move host to maintenance if not active
Keywords:
Status: CLOSED DUPLICATE of bug 1574443
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Martin Perina
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-29 09:54 UTC by Sandro Bonazzola
Modified: 2019-08-23 08:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-23 08:28:21 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.3+

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.