Details
-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.13.0, 4.12.0, 4.11.0, 4.10.0, 4.9.0
-
Moderate
-
Sprint 233
-
1
-
False
-
Description
Description of problem:
When the IBMCOS storage type is used but the config itself is empty, it causes the cluster-image-registry-operator to fall into a crashloop due to NPE.
Version-Release number of selected component (if applicable):
How reproducible:
Can be reproduced easily.
Steps to Reproduce:
1. Create an OpenShift cluster on 4.9+
2. Alter the image registry storage config to use "spec.storage.ibmcos: {}"
3. Watch the cluster-image-registry-operator crashloop
Actual results:
The cluster-image-registry-operator pod constantly in a crashloop.
Expected results:
The cluster-image-registry-operator pod to run without issues.
Additional info:
https://github.com/openshift/cluster-image-registry-operator/issues/835
