Description of problem: It's a bit confusing, that there is event 'Host <host> upgrade was completed successfully' and then the host is rebooted in the same time. I think that 'the upgrade was completed' event should wait for the host to get back to state, from where the upgrade was started (in my case up). From my point of view, restarting is a part of upgrade process. What if rebooting will fail from any reason? (for example host will hang in PXE or in shutdown process) Version-Release number of selected component (if applicable): ovirt-ansible-cluster-upgrade-1.1.12-1.el7ev.noarch How reproducible: always Steps to Reproduce: 1. run cluster upgrade (with reboot) and correlate events with states of the host additional info: please notice times of rebooting and upgrade: 2:32:04 PM Upgrade of cluster Default finished successfully. 2:31:44 PM Status of host host-03 was set to Up. 2:26:37 PM Host host-03 upgrade was completed successfully. 2:26:37 PM Host host-03 was restarted using SSH by the engine. 2:25:45 PM Host host-03 was switched to Maintenance Mode. 2:25:45 PM Host host-03 upgrade was started (User: admin@internal-authz). 2:25:43 PM check for available updates on host host-03 was completed successfully with message 'found updates for packages vim-common, vim-enhanced'. 2:25:17 PM Started to check for available updates on host host-03.
Verified in ovirt-engine-4.3.4.2-0.1.el7.noarch
This bugzilla is included in oVirt 4.3.4 release, published on June 11th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.4 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.