-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
None
-
4.12
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
Proposed
-
CMP Sprint 54, CMP Sprint 55
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Installing the Compliance Operator through the UI in OperatorHub hangs.
Version-Release number of selected component (if applicable):
$ oc version Client Version: 4.11.4 Kustomize Version: v4.5.4 Server Version: 4.12.0-0.nightly-2022-10-05-053337 Kubernetes Version: v1.25.0+3ef6ef3
How reproducible:
You can reproduce by attempting to install the Compliance Operator through the OperatorHub UI on a 4.12 OCP cluster.
Steps to Reproduce:
1. Deploy an OCP 4.12 cluster 2. Navigate to the OperatorHub pane 3. Filter available operators by "Compliance Operator" 4. Select the "Compliance Operator" and install version 0.1.53
Actual results:
The installation eventually fails with:
The pod fails with the following error message, causing the deployment to not come up.
Back-off pulling image "registry.redhat.io/compliance/openshift-compliance-rhel8-operator@sha256:43c06aae0ccacc460ecb9731c5bb25d075e7f0cf6f105dbe49aa1d31ca0513c2"
Expected results:
The operator should install successfully.
Additional info:
