Bug 1935715

Summary:	test: Detect when the master pool is still updating after upgrade
Product:	OpenShift Container Platform	Reporter:	Vadim Rutkovsky <vrutkovs>
Component:	Test Infrastructure	Assignee:	Vadim Rutkovsky <vrutkovs>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.6	CC:	ccoleman
Target Milestone:	---
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1935707	Environment:
Last Closed:	2021-12-17 12:30:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1935707
Bug Blocks:

Description Vadim Rutkovsky 2021-03-05 12:51:18 UTC

+++ This bug was initially created as a clone of Bug #1935707 +++

+++ This bug was initially created as a clone of Bug #1935706 +++

The MCO is required to roll out the master config pool prior to reporting level, and thus CVO should never reach Available at a
new version without the master pool being updated. Add an extra check to the pool rollout - if we see the master pool with an
Updating condition flag it and fail the upgrade job. Also handle paused pools in the wait loop (a paused pool is effectively "we
will not deal with this pool" and so we will exit early and log).

--- Additional comment from Vadim Rutkovsky on 2021-03-05 12:33:29 UTC ---

Fixed in https://github.com/openshift/origin/pull/25922

Comment 2 Vadim Rutkovsky 2021-12-17 12:30:21 UTC

No longer occuring