Description of problem: On a two nodes cluster, the cluster upgrade fails because tries to put on maintenance mode a node while the last updated is rebooting. Version-Release number of selected component (if applicable): How reproducible: * Create a two node cluster. * Update the two nodes through Upgrade Cluster button [1]. Actual results: Only updates one node, the another one stays on "Inactive" mode. Expected results: Both nodes been updated. Additional info: ovirt-engine release: 4.5.3.5 ovirt-ansible-collection: 2.3.0-1 [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/upgrade_guide/index#Updating_all_hosts_in_a_cluster_minor_updates
This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).
What version of the ovirt-ansible-collection are you using?
Hello Martin, Here is the rpm output, ovirt-ansible-collection-2.3.0-1.el8ev.noarch Thu Nov 17 13:11:44 2022
*** Bug 2149340 has been marked as a duplicate of this bug. ***
One host is waiting for the other host to be in result state and the cluster upgrade does not fail and both hosts are updated. Verified in ovirt-ansible-collection-2.4.2-1.el8ev.noarch and ovirt-engine-4.5.3.7-0.zstream.20230125101610.gitf21a4b1784d.el8.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Virtualization security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:0759