conflicting CRD owner in namespace reported during Operator update in OpenShift Container Platform 4

Issue

• After the successful OpenShift cluster update some operators are stuck in can not upgrade or failing state.
• Operator update is failing with the below error:

2020-02-25T15:32:25.437397306Z E0325 15:32:25.437352       1 queueinformer_operator.go:290] sync {"update" "openshift-operators/elasticsearch-operator.4.3.7-202003190458"} failed: conflicting CRD owner in namespace
2020-02-25T15:32:25.439423986Z time="2020-02-25T15:32:25Z" level=info msg="csv in operatorgroup" csv=elasticsearch-operator.4.3.7-202003190458 id=gU5un namespace=openshift-operators opgroup=global-operators phase=Failed
2020-02-25T15:32:25.439463278Z time="2020-02-25T15:32:25Z" level=info msg="updated annotations to match current operatorgroup" csv=elasticsearch-operator.4.3.7-202003190458 id=gU5un namespace=openshift-operators phase=Failed
2020-02-25T15:32:25.44765321Z time="2020-02-25T15:32:25Z" level=warning msg="needs reinstall: ComponentMissing: missing deployment with name=elasticsearch-operator" csv=elasticsearch-operator.4.3.7-202003190458 id=gU5un namespace=openshift-operators phase=Failed strategy=deployment
2020-02-25T15:32:26.038125242Z time="2020-02-25T15:32:26Z" level=info msg="csv in operatorgroup" csv=elasticsearch-operator.4.3.7-202003190458 id=1nJNk namespace=openshift-operators opgroup=global-operators phase=Pending