Quay TNG Operator deployment was failed on OCP 4.4

Description:

This is an issue found when deploy Quay V3.4 TNG Operator on OCP 4.4,  after select all default options(see screenshot-'Quay Operator deployment options'), deployment was failed with error message "one or more requirement couldn't be found", checked OCP OLM logs, get error message as the following, more details refer to OLM logs attached.

time="2020-11-16T09:38:08Z" level=info msg="couldn't ensure RBAC in target namespaces" csv=quay-operator.v3.4.0 error="no owned roles found" id=/Bo6l namespace=openshift-operators phase=Pending
E1116 09:38:08.841493       1 queueinformer_operator.go:290] sync {"update" "openshift-operators/quay-operator.v3.4.0"} failed: no owned roles found

Note: 

• If choose to deploy quay operator to specific OCP namespace, it works well.
• On OCP 4.6, this issue was not existed.

OCP Version:

4.4.0-0.nightly-2020-11-15-105926

Index image:

Index image v4.5: registry-proxy.engineering.redhat.com/rh-osbs/iib:25554

Quay Operator Image:

[root@ip-10-0-1-60 centos]# oc get csv quay-operator.v3.4.0 -o json | jq '.metadata.annotations.containerImage'
"registry.redhat.io/quay/quay-rhel8-operator@sha256:4a701574c98f7a95a2f50efbe17856d5b817c6c126aa3c3524714c631f09bf8f"

Steps:

1. On OCP 4.4 click OCP Operator Hub
2. Choose Quay 3.4 operator to deploy
3. with all default settings, click subscribe
4. check quay operator deployment status

Expected Results:

Quay operator deployment complete successfully.

Actual Results:

Quay operator deployment was failed with error message "one or more requirement couldn't be found"