elasticsearch-operator failed in automatic upgrade to elasticsearch-operator.4.2.4-201911050122

When we have an existing Elasticsearch-operator installed on an OCP 4.3 cluster, the automatic upgrade failed to upgrade ES operator to version 4.2.4-201911050122.

From OCP console Installed Operators UI, it shows new version of ES operator failed to upgrade and existing version of ES operator in Failed Status with a message:

Failed: conflicting CRD owner in namespace message

In the other hand, we can do a fresh installation of ES operator 4.2.4-201911050122 successfully.

Environment: OCP 4.3 openshift-install-linux-4.3.0-0.nightly-2019-11-13-103541 AWS
Existing ES operator version: ( I lost the previous ES operator version after uninstallation. It was an ES operator installed yesterday.)
Latest target ES operator version: 4.2.4-201911050122

How to produce:
1. install an old ES operator on an OCP cluster with automatic upgrade mode
2. Wait to see ES operator under an upgrade process.
3. Check upgrade status

Expected result:
ES operator should complete upgrade successfully.