Bug 1383224

Summary: RHVH-NG is automatically activated after upgrade.
Product: Red Hat Enterprise Virtualization Manager Reporter: Roman Hodain <rhodain>
Component: ovirt-engineAssignee: Moti Asayag <masayag>
Status: CLOSED ERRATA QA Contact: Pavol Brilla <pbrilla>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.3CC: amarchuk, bazulay, dfediuck, dougsland, emesika, fdeutsch, gklein, lsurette, mgoldboi, mperina, oourfali, pstehlik, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ovirt-4.1.0-alphaKeywords: Regression, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1394508 (view as bug list) Environment:
Last Closed: 2017-04-25 00:45:56 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:
Bug Depends On:    
Bug Blocks: 1394508    

Description Roman Hodain 2016-10-10 08:50:15 UTC
Description of problem:
RHVH-NG is automatically activated after upgrade even if the hosts was previously in the maintenance mode. Standard RHEL-H remains in maintenance after the upgrade if it was previously in that state. 

Version-Release number of selected component (if applicable):
ovirt-host-deploy-java-1.5.2-1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Put RHV-H-ng to maintenance mode
2. Press Upgrade button in WebAdmin portal


Actual results:
The hosts is automatically started after the upgrade

Expected results:
Th host remains in the maintenance mode if it was inthis mode before the upgrade process started.

Comment 1 Sandro Bonazzola 2016-10-11 07:08:26 UTC
I think this is a duplicate of bug 1380797 but I'll let node team to investigate.

Comment 3 Fabian Deutsch 2016-10-11 10:35:49 UTC
To my understanding the state of a host is handled in Engine.

Eli, do you know if the flow for Node after updates is different than for RHEL hosts?

Comment 4 Ryan Barry 2016-10-11 12:52:25 UTC
I'm also curious where any local information (on the host) about state may be if this is not handled in engine.

Comment 5 Eli Mesika 2016-10-13 07:17:47 UTC
Problem is in engine , taking the bug ....

Comment 6 Martin Perina 2016-10-18 11:43:10 UTC
Moving back to Eli per Comment 5

Comment 7 Martin Perina 2016-10-25 08:53:42 UTC
It's not critical issue, moving to 4.0.6

Comment 9 Pavol Brilla 2017-02-13 15:05:29 UTC
Host put to maintenance, update done successfully, after reboot server is back in maintenance,

Red Hat Virtualization Manager Version: 4.1.0.4-0.1.el7
Update between beta 4.1 rhvh versions