Description of problem (please be detailed as possible and provide log
snippests):

When installing OpenShift Container Storage from OLM on OpenShift 4.3 the noobaa-core-0 and noobaa statefulset pods for PV Pools are created using an upstream image.


Version of all relevant components (if applicable):
4.2.1

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
It works, but our requirement to work in disconnected/restricted network environments is limited due to this issue.

Is there any workaround available to the best of your knowledge?
No.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes.

Can this issue reproduce from the UI?
No.

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Install OCS operator
2. Create a NooBaa System
3. Create a PV Pool Backing Store

apiVersion: noobaa.io/v1alpha1
kind: BackingStore
metadata:
  finalizers:
  - noobaa.io/finalizer
  labels:
    app: noobaa
  name: mcg-pv-pool-bs
  namespace: openshift-storage
spec:
  pvPool:
    numVolumes: 3
    resources:
      requests:
        storage: 50Gi
    storageClass: gp2
  type: pv-pool

Actual results:
The downstream operator:
$ oc describe po noobaa-operator-59894b6668-l6l6s | grep Image
    Image:          registry.redhat.io/ocs4/mcg-rhel8-operator@sha256:ecb1c4e486aca77bda000fa71d190f90e06173447cff1bed983fb6e246975863
    Image ID:       registry.redhat.io/ocs4/mcg-rhel8-operator@sha256:ecb1c4e486aca77bda000fa71d190f90e06173447cff1bed983fb6e246975863

is creating the noobaa core and statefulset pods using upstream images:
$ oc describe po mcg-pv-pool-bs-noobaa-noobaa-2 | grep Image
    Image:         noobaa/noobaa-core:5.2.11
    Image ID:      docker.io/noobaa/noobaa-core@sha256:4389a1bb98083946b7837837613e7e64829333b166a2acd664093ced3e034fa6

$ oc describe po mcg-pv-pool-bs-noobaa-noobaa-2 | grep Image
    Image:         noobaa/noobaa-core:5.2.11
    Image ID:      docker.io/noobaa/noobaa-core@sha256:4389a1bb98083946b7837837613e7e64829333b166a2acd664093ced3e034fa6
[jmontleo@jmontleo mig-operator]$ oc describe po noobaa-core-0 | grep Image
    Image:         noobaa/noobaa-core:5.2.11
    Image ID:      docker.io/noobaa/noobaa-core@sha256:4389a1bb98083946b7837837613e7e64829333b166a2acd664093ced3e034fa6
    Image:          noobaa/noobaa-core:5.2.11
    Image ID:       docker.io/noobaa/noobaa-core@sha256:4389a1bb98083946b7837837613e7e64829333b166a2acd664093ced3e034fa6
    Image:         centos/mongodb-36-centos7
    Image ID:      docker.io/centos/mongodb-36-centos7@sha256:48a9fc021f16138cda94dc36914610df78caac36d751218ae499cc9c6363194b

Expected results:
The noobaa core and statefulset pods are created using the downstream images referenced in the CSV:
registry.redhat.io/ocs4/mcg-core-rhel8@sha256:1906a018df2774f1d0338483255c5f314fe707afcf12271f53a346790de9fdcf
registry.redhat.io/rhscl/mongodb-36-rhel7@sha256:506e4daa19721199e35249f2e0e67b02cbcbee1fed653f7eb91d5595b74c3bf8

Additional info:
Tying into https://bugzilla.redhat.com/show_bug.cgi?id=1798052 tags cannot be used to mirror images in OpenShift 4 because mirror by tag is turned off in OpenShift 4 cri-o, making it impossible to use noobaa in a disconnected environment even if you do determine the list of images to mirror and do so manually.