Operator upgrade is failing with "conflicting CRD owner in namespace" on OpenShift Container Platform 4

Issue

• After the automated update of all Operators in the OpenShift cluster, the following issue was found and the OpenShift Pipelines operator update is stuck/failing (the same problem was seen with other Operators as well).

  $ oc get events -n openshift-operators
  LAST SEEN   TYPE      REASON           OBJECT                                                          MESSAGE
  1m39s       Warning   OwnerConflict    clusterserviceversion/openshift-pipelines-operator-rh.v1.10.2   conflicting CRD owner in namespace
  6m          Normal    NeedsReinstall   clusterserviceversion/openshift-pipelines-operator-rh.v1.10.2   installing: missing deployment with name=openshift-pipelines-operator
  1m43s       Warning   OwnerConflict    clusterserviceversion/openshift-pipelines-operator-rh.v1.10.3   conflicting CRD owner in namespace
  6m          Normal    NeedsReinstall   clusterserviceversion/openshift-pipelines-operator-rh.v1.10.3   installing: missing deployment with name=openshift-pipelines-operator
  

• Operator update on OpenShift is stuck and reporting conflicting crd owner in namespace event.

• While searching for conflicting crd owner in namespace event, we came across conflicting CRD owner in namespace reported during Operator update in OpenShift Container Platform 4 but found this not to be relevant anymore and thus wondering how to address that problem?