Bug 2161703

Summary:	[RHEVM] Two nodes cluster upgrade failed, tries to put a node into maintenance while the updated is rebooting
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	José Enrique <josgutie>
Component:	ovirt-ansible-collection	Assignee:	Martin Necas <mnecas>
Status:	CLOSED ERRATA	QA Contact:	Barbora Dolezalova <bdolezal>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.5.3	CC:	bdolezal, emarcus, lleistne, mavital, mperina
Target Milestone:	ovirt-4.5.3-async	Keywords:	AutomationBlocker, Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-ansible-collection-2.4.2	Doc Type:	Bug Fix
Doc Text:	With this release, the upgrade function of the ovirt_host module waits long enough for the upgraded host to reach the desired state after upgrade.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-02-14 13:09:16 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:

Description José Enrique 2023-01-17 16:43:00 UTC

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

Comment 1 Casper (RHV QE bot) 2023-01-17 17:00:52 UTC

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).

Comment 2 Martin Necas 2023-01-18 12:25:36 UTC

What version of the ovirt-ansible-collection are you using?

Comment 3 José Enrique 2023-01-19 12:02:45 UTC

Hello Martin,

Here is the rpm output,
ovirt-ansible-collection-2.3.0-1.el8ev.noarch               Thu Nov 17 13:11:44 2022

Comment 4 Martin Perina 2023-01-24 14:55:18 UTC

*** Bug 2149340 has been marked as a duplicate of this bug. ***

Comment 7 Barbora Dolezalova 2023-02-06 09:52:01 UTC

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

Comment 9 errata-xmlrpc 2023-02-14 13:09:16 UTC

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