Bug 1935706 - test: Detect when the master pool is still updating after upgrade
Summary: test: Detect when the master pool is still updating after upgrade
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Infrastructure
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Clayton Coleman
QA Contact:
Depends On:
Blocks: 1935707
TreeView+ depends on / blocked
Reported: 2021-03-05 12:32 UTC by Vadim Rutkovsky
Modified: 2021-07-27 22:52 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1935707 (view as bug list)
Last Closed: 2021-07-27 22:51:38 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:52:05 UTC

Description Vadim Rutkovsky 2021-03-05 12:32:42 UTC
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).

Comment 1 Vadim Rutkovsky 2021-03-05 12:33:29 UTC
Fixed in https://github.com/openshift/origin/pull/25922

Comment 4 errata-xmlrpc 2021-07-27 22:51:38 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: OpenShift Container Platform 4.8.2 bug fix and security 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.


Note You need to log in before you can comment on or make changes to this bug.