Bug 2010662 - Cluster is unhealthy after image-registry-operator tests
Summary: Cluster is unhealthy after image-registry-operator tests
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Oleg Bulatov
QA Contact: wewang
Depends On:
Blocks: 2023219
TreeView+ depends on / blocked
Reported: 2021-10-05 10:08 UTC by Oleg Bulatov
Modified: 2022-03-10 16:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:16:32 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-image-registry-operator pull 726 0 None open WIP Bug 2010662: Wait until cluster operators recover before proceeding 2021-10-18 13:30:23 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:16:43 UTC

Description Oleg Bulatov 2021-10-05 10:08:18 UTC
Description of problem:

The image-registry-operator tests leave the cluster in unhealthy state. As a result, the must-gather step cannot collect information and fails the entire job.

Version-Release number of selected component (if applicable):


How reproducible:

Almost always.

Steps to Reproduce:
1. run e2e-aws-operator in cluster-image-registry-operator

Actual results:

The must-gather step fails to collect information and lots of operators are degraded/unavailable.

Expected results:

Green tests.

Example of a failed job:


Comment 1 wewang 2021-10-27 00:18:16 UTC
Now pr is in wip status, will check it later

Comment 6 errata-xmlrpc 2022-03-10 16:16:32 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.10.3 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.