Bug 1935715 - test: Detect when the master pool is still updating after upgrade
Summary: test: Detect when the master pool is still updating after upgrade
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Infrastructure
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.6.z
Assignee: Vadim Rutkovsky
QA Contact:
URL:
Whiteboard:
Depends On: 1935707
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-05 12:51 UTC by Vadim Rutkovsky
Modified: 2021-12-17 12:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1935707
Environment:
Last Closed: 2021-12-17 12:30:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.