Description of problem: RHVH upgrade requires properly configured power-management or manual restart during upgrade from 4.1 to 4.2. During upgrade, the host was not able to get restarted from UI, as I did not configured remote power management. Failed to upgrade Host alma03.qa.lab.tlv.redhat.com (User: admin@internal-authz). 6/25/183:03:31 PM  Failed to upgrade Host alma03.qa.lab.tlv.redhat.com (User: admin@internal-authz). 6/25/183:03:28 PM Host alma03.qa.lab.tlv.redhat.com was switched to Maintenance Mode. 6/25/182:33:24 PM  Host alma03.qa.lab.tlv.redhat.com upgrade was started (User: admin@internal-authz). 6/25/182:33:24 PM  Check for available updates on host alma03.qa.lab.tlv.redhat.com was completed successfully with message 'found updates for packages redhat-virtualization-host-image-update'. 6/25/182:30:54 PM  Host alma03.qa.lab.tlv.redhat.com has available updates: redhat-virtualization-host-image-update. 6/25/182:30:54 PM  Started to check for available updates on host alma03.qa.lab.tlv.redhat.com. 6/25/182:30:36 PM  Status of host alma03.qa.lab.tlv.redhat.com was set to Up. 6/25/182:26:50 PM During upgrade, the host was not able to get restarted from UI, as I did not configured remote power management. I've restarted it manually and after that, host seamed upgrading something and then it got rebooted on its own again and then started with black screen and did not let me to log in for a few minutes (15-20), then I received the login prompt. I tried to activate the host from UI and host successfully activated. Check for available updates on host alma03.qa.lab.tlv.redhat.com was completed Version-Release number of selected component (if applicable): 4.1RHVH's components: ovirt-hosted-engine-ha-2.1.11-1.el7ev.noarch ovirt-hosted-engine-setup-2.1.4.2-1.el7ev.noarch Linux 3.10.0-862.el7.x86_64 #1 SMP Wed Mar 21 18:14:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 7.5-0.14 4.2RHVH's components: ovirt-hosted-engine-setup-2.2.22-1.el7ev.noarch ovirt-hosted-engine-ha-2.2.14-1.el7ev.noarch Linux 3.10.0-862.6.3.el7.x86_64 #1 SMP Fri Jun 15 17:57:37 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 7.5 How reproducible: 100% Steps to Reproduce: 1.Deployed SHE on 4.1RHVH. Components on host: ovirt-hosted-engine-ha-2.1.11-1.el7ev.noarch ovirt-hosted-engine-setup-2.1.4.2-1.el7ev.noarch Linux 3.10.0-862.el7.x86_64 #1 SMP Wed Mar 21 18:14:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 7.5-0.14 2.Added additional 4.1RHVH as ha-host. 3.Checked for upgrade for one of the hosts via UI. 4.Upgrade 4.1RHVH from UI to 4.2RHVH by clicking "Install"->"Upgrade". Actual results: Failed to upgrade Host is displayed in logs in UI. Expected results: User should be properly warned that proper host's reboot is mandatory, so customer will be able to properly configure power management for all RHVHs. Additional info: Please see https://bugzilla.redhat.com/show_bug.cgi?id=1585028#c22 for more details.
Ondro, we are restarting hosts after upgrade in RHV 4.2 using SSH and not power management, right? If so, then I suggest to close it as not a bug
Martin, All of the host upgrade procedures in the current Upgrade Guide say "After the upgrade, the host is restarted." Is there any reason to change the text? Example: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/upgrade_guide/#Proc-Updating-Linux-Hosts-4_0
(In reply to Martin Perina from comment #1) > Ondro, we are restarting hosts after upgrade in RHV 4.2 using SSH and not > power management, right? If so, then I suggest to close it as not a bug Yes, we are restarting hosts via SSH.
Closing bug, as per comment 1.