When I use `oc-mirror` to sync operator image to local registry, it fails 

    4.16

    CMD:/opt/dci-quay/artifacts/ocp-stable/oc-mirror --config=/opt/dci-quay/artifacts/files/imageset-config-OCP-4.16.yml docker://dci-mirror-registry.rackg06.local/raven-operators --skip-cleanup --skip-pruning

1. prepare registry and oc-mirror fist    
2. create yaml file imageset-config-OCP-4.16.yml
kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v1alpha2
storageConfig:
  registry:
    imageURL: dci-mirror-registry.rackg06.local/raven-operators/oc-mirror-metadata
    skipTLS: true
mirror:
  operators:
  - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.15
    packages:
    - name: cincinnati-operator
      channels:
      - name: v1
    - name: servicemeshoperator
      channels:
      - name: stable
    - name: openshift-secondary-scheduler-operator
      channels:
      - name: stable
    - name: metallb-operator
      channels:
      - name: stable
2.oc-mirror --config=/opt/dci-quay/artifacts/files/imageset-config-OCP-4.16.yml docker://dci-mirror-registry.rackg06.local/raven-operators --skip-cleanup --skip-pruning      

skipped pruning
Rendering catalog image "dci-mirror-registry.rackg06.local/raven-operators/redhat/redhat-operator-index:v4.15" with file-based catalog
error: error rebuilding catalog images from file-based catalogs: error regenerating the cache for dci-mirror-registry.rackg06.local/raven-operators/redhat/redhat-operator-index:v4.15: exit status 1   

    successfully exit

    We are leveraging this in DCI pipeline. The step to reproduce is automatically driven by DCI.