After the outage CVP pipeline on April 10 - The operator OLM deployment test to not be run for DWO 0.27.0 - however, the last successful CVP report was for devworkspace-operator-bundle-container-0.27-3 which was actually based on DWO 0.26.0 upstream.
The recommended QE action items:
For every DWO 0.27 IIB and it's associated OCP version, we need to configure a catalog source that accesses the IIBs from Brew and create an OLM subscription. The OLM subscription needs to suceed within 10 minutes.
Since we are claiming FIPS compliance, we need to also consider testing in a FIPS enabled cluster.
Need to be tested:
Index image v4.12: registry-proxy.engineering.redhat.com/rh-osbs/iib:706446
Index image v4.13: registry-proxy.engineering.redhat.com/rh-osbs/iib:706457
Index image v4.14: registry-proxy.engineering.redhat.com/rh-osbs/iib:706474
Index image v4.15: registry-proxy.engineering.redhat.com/rh-osbs/iib:706490
Index image v4.16: registry-proxy.engineering.redhat.com/rh-osbs/iib:706502