Image-registry doesn't exist in OCP 4.3 deployment over VmWare

[petr-balogh]

Looks like we have issue with image-registry:
elif len(pod_obj) == 0:

          raise UnexpectedBehaviour("Image-registry pod not present")

E ocs_ci.ocs.exceptions.UnexpectedBehaviour: Image-registry pod not present

Martin Bukatovic pointed out when we had some discussion that he found this documentation: https://docs.openshift.com/container-platform/4.3/registry/configuring-registry-operator.html#registry-removed_configuring-registry-operator

Based on docs it looks to me that this image-registry has managedState set to Removed on not cloud providers and causing issue in our deployment on VmWare with OCP 4.3.
@ramakrishnan Periyasamy are you aware of this?
When I ran command: oc patch configs.imageregistry.operator.openshift.io/cluster --type merge -p '{"spec":{"managementState": "Managed"}}'
it looks like I have image registry now:

[jenkins@temp-jslave-pbalogh43ga image_registry_logs]$ oc -n openshift-image-registry --kubeconfig /home/jenkins/current-cluster-dir/openshift-cluster-dir/auth/kubeconfig get Pod  -n openshift-image-registry --selector=docker-registry=default
NAME                              READY   STATUS    RESTARTS   AGE
image-registry-67b9cd8c49-qwndg   1/1     Running   0          100s

So I guess we have to add this command to our deployment when deploy over VmWare.

[petr-balogh]

Running verification here: https://ocs4-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/qe-deploy-ocs-cluster/4322/console