Operator is not updated when changing the channel to a greater version.

Hello 

I have a case where in a disconnected environment the customer mirrors specific operator versions of gitops operator and after changing the channel to latest or the latest channel (currently gitops-1.8) the operator is not upgraded. No logs in catalog operator pod or OLM operator pod. No install plan or any other action happens in the cluster.

In more detail.

• Created registry to mirror the images and a cluster version v.4.11.36
• I mirrored using the imageset file below:

kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v1alpha2
storageConfig:
  local:
    path: /opt/gitops-versions/gitops
mirror:
  operators:
    - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.11
      packages:
        - name: openshift-gitops-operator
          channels:
            - name: latest
            - name: gitops-1.6
              minVersion: '1.6.1'
              maxVersion: '1.6.1'
            - name: gitops-1.7
              minVersion: '1.7.2'
              maxVersion: '1.7.2'
            - name: gitops-1.8
              minVersion: '1.8.3'
              maxVersion: '1.8.3'

• I got the packagemanifests of these versions correctly in the cluster with the catalogSource image generated from the oc-mirror.
• I installed the gitops operator with version "v1.6.1-0.1666124167.p" by subscribing it to channel "gitops-1.6"
• I was able to see all mirrored channels in the Web Console UI under the operator.
• I then subscribed the operator to latest channel. Nothing happened!
• I then subscribed the operator to gitops-1.8 channel. Nothing happened!
• I then subscribed the operator to gitops-1.7 channel. The operator upgraded to v1.7.2

I tried the same test in a connected cluster where the full Red Hat Operators Catalog index is available and the issue did not reproduce. Everything was normal. 

Actual result. The operator is not upgraded.

Expected result. The operator should be upgraded