-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
4.13.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
up to the documentation the image "quay.io/compliance-operator/must-gather" should get used to gather data for support cases. As this image is not a related image in the operators spec, this image will not get automatically pulled/mirrored. I case of a disconnected cluster this leads the related must-gather image likely not being available. As this get mostly not discovered during usual usage, but in case of a crisis, this needs to get avoided
Version-Release number of selected component (if applicable):
all, AFAIK
How reproducible:
always on any disconnected cluster or by checking the redhat-operator-index
Steps to Reproduce:
1. opm render registry.redhat.io/redhat/redhat-operator-index:v4.13 > redhat-operator-index-v4.13.json
2. operatorNames=$(jq 'select(.schema == "olm.bundle") | select ( .relatedImages[].image | contains ("quay.io/compliance-operator/must-gather")) | .name' redhat-operator-index-v4.13.json )
Actual results:
no operator has "quay.io/compliance-operator/must-gather" as related image
Expected results:
"compliance-operator.v*" is expected to have a related image "quay.io/compliance-operator/must-gather*"
Additional info: