Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2149340

Summary:	Cluster upgrade marked as completed successfully before all hosts are upgraded
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Barbora Dolezalova <bdolezal>
Component:	ovirt-ansible-collection	Assignee:	Martin Necas <mnecas>
Status:	CLOSED DUPLICATE	QA Contact:	Barbora Dolezalova <bdolezal>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.5.3	CC:	mavital, michal.skrivanek, mperina
Target Milestone:	---	Keywords:	AutomationBlocker, Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-24 14:55:18 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 Barbora Dolezalova 2022-11-29 16:10:52 UTC

Description of problem:
Cluster upgrade with more hosts that have upgrade available is marked as successful when the hosts are still upgrading. 

Version-Release number of selected component (if applicable):
ovirt-ansible-collection-2.4.1-1.el8ev.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Cluster with three hosts that have upgrade available
2. Run cluster upgrade role on that cluster

Actual results:
The role cluster upgrade successfully ended with two hosts still rebooting. The engine marks them as successfully upgraded after the reboot.

Expected results:
The role cluster upgrade successfully ended after the engine marks all the hosts as successfully upgraded.


Additional info:
When one host runs hosted engine vm the upgrade won't start because Failed to switch Host xx to Maintenance mode.
Works the same when running in UI.

Comment 1 Barbora Dolezalova 2022-11-29 16:12:36 UTC

Could be connected with BZ 2036613

Comment 5 Michal Skrivanek 2022-12-02 07:48:15 UTC

when was the last time this used to pass?

Comment 6 Barbora Dolezalova 2022-12-06 09:20:30 UTC

I don't know exactly because it was hidden behind this BZ 2142601.

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


*** This bug has been marked as a duplicate of bug 2161703 ***