The oc-mirror init command produces a sample imageset-config.yaml which references the incorrect release. In this case 4.17 instead of 4.16

    100%

Run the command: oc-mirror init --registry ip-10-0-170-23.us-east-2.compute.internal:8443 > imageset-config.yaml
    

    The imageset-config.yaml looks like this


kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v1alpha2
storageConfig:
  registry:
    imageURL: ip-10-0-170-23.us-east-2.compute.internal:8443
    skipTLS: false
mirror:
  platform:
    channels:
    - name: stable-4.16
      type: ocp
  operators:
  - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.17
    packages:
    - name: serverless-operator
      channels:
      - name: stable
  additionalImages:
  - name: registry.redhat.io/ubi8/ubi:latest
  helm: {}

    An imageset-config.yaml that references the correct release like

kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v1alpha2
storageConfig:
  registry:
    imageURL: ip-10-0-170-23.us-east-2.compute.internal:8443
    skipTLS: false
mirror:
  platform:
    channels:
    - name: stable-4.16
      type: ocp
  operators:
  - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.16
    packages:
    - name: serverless-operator
      channels:
      - name: stable
  additionalImages:
  - name: registry.redhat.io/ubi8/ubi:latest
  helm: {}

    Using the oc-mirror 4.16 stable release is producing a same imageset-config.yaml that has links to the redhat-operator-index:v4.17 instead of v4.16 which causes errors during the actual mirroring process. The errors that result are not super helpful so it is difficult for users to track down what went wrong which, in this case, is a single digit in the sample config file.