At release, we found that some operands had not shipped where they were expected according to bundle references.

• ose-gcp-filestore-csi-driver-operator-bundle-container-v4.12.0.202301042354.p0.g7ed738d.assembly.stream-1 referred to:
  • registry.redhat.io/openshift4/ose-gcp-filestore-csi-driver-operator which should have been registry.redhat.io/openshift4/ose-gcp-filestore-csi-driver-rhel8-operator
  • registry.redhat.io/openshift4/ose-gcp-filestore-csi-driver which should have been registry.redhat.io/openshift4/ose-gcp-filestore-csi-driver-rhel8
• ose-ptp-operator-metadata-container-v4.12.0.202301050335.p0.g9008db8.assembly.stream-1 referred to:
  • registry.redhat.io/openshift4/ose-cloud-event-proxy which should have been registry.redhat.io/openshift4/ose-cloud-event-proxy-rhel8
• ingress-node-firewall-operator-bundle-container-v4.12.0.202301042354.p0.g3c81f59.assembly.stream-1 referred to:
  • registry.redhat.io/openshift4/ingress-node-firewall-daemon which should have been registry.redhat.io/openshift4/ingress-node-firewall
  • registry.redhat.io/openshift4/ingress-node-firewall-operator which should have been registry.redhat.io/openshift4/ingress-node-firewall-rhel8-operator

Customers could use an ICSP to fix these up at run time but this bug should be used to ship fixed bundles that will work from operatorhub without workarounds.