Bug 1383224 - RHVH-NG is automatically activated after upgrade.
Summary: RHVH-NG is automatically activated after upgrade.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.1.0-alpha
: ---
Assignee: Moti Asayag
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On:
Blocks: 1394508
TreeView+ depends on / blocked
 
Reported: 2016-10-10 08:50 UTC by Roman Hodain
Modified: 2020-02-14 18:00 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1394508 (view as bug list)
Environment:
Last Closed: 2017-04-25 00:45:56 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1380797 0 urgent CLOSED Node upgrade doesn't keep service enable/disable configuration 2021-06-10 11:40:59 UTC
Red Hat Product Errata RHEA-2017:0997 0 normal SHIPPED_LIVE Red Hat Virtualization Manager (ovirt-engine) 4.1 GA 2017-04-18 20:11:26 UTC
oVirt gerrit 65802 0 None None None 2016-10-27 12:18:57 UTC

Internal Links: 1380797

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