Seeing errors when trying to perform delete using the new release collector for delete feature
2024/08/05 10:44:58  [ERROR]  : [Worker] error mirroring image docker://registry.redhat.io/ubi8-minimal@sha256:b93deceb59a58588d5b16429fc47f98920f84740a1f2ed6454e33275f0701b59 error: Unable to delete ec2-18-218-239-117.us-east-2.compute.amazonaws.com:5000/clid-99/ubi8-minimal:b93deceb59a58588d5b16429fc47f98920f84740a1f2ed6454e33275f0701b59. Image may not exist or is not stored with a v2 Schema in a v2 registry
2024/08/05 10:44:58  [ERROR]  : [Worker] error mirroring image docker://registry.redhat.io/ubi8-minimal@sha256:b93deceb59a58588d5b16429fc47f98920f84740a1f2ed6454e33275f0701b59 error: Unable to delete ec2-18-218-239-117.us-east-2.compute.amazonaws.com:5000/clid-99/ubi8-minimal:b93deceb59a58588d5b16429fc47f98920f84740a1f2ed6454e33275f0701b59. Image may not exist or is not stored with a v2 Schema in a v2 registry
2024/08/05 10:44:58  [ERROR]  : [Worker] error mirroring image docker://registry.redhat.io/ubi8-minimal@sha256:b93deceb59a58588d5b16429fc47f98920f84740a1f2ed6454e33275f0701b59 error: Unable to delete ec2-18-218-239-117.us-east-2.compute.amazonaws.com:5000/clid-99/ubi8-minimal:b93deceb59a58588d5b16429fc47f98920f84740a1f2ed6454e33275f0701b59. Image may not exist or is not stored with a v2 Schema in a v2 registry
2024/08/05 10:44:58  [ERROR]  : [Worker] error mirroring image docker://registry.redhat.io/ubi8-minimal@sha256:b93deceb59a58588d5b16429fc47f98920f84740a1f2ed6454e33275f0701b59 error: Unable to delete ec2-18-218-239-117.us-east-2.compute.amazonaws.com:5000/clid-99/ubi8-minimal:b93deceb59a58588d5b16429fc47f98920f84740a1f2ed6454e33275f0701b59. Image may not exist or is not stored with a v2 Schema in a v2 registry
    

    [fedora@preserve-fedora-yinzhou test]$ ./oc-mirror version
WARNING: This version information is deprecated and will be replaced with the output from --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"", Minor:"", GitVersion:"v0.2.0-alpha.1-280-g8a42369", GitCommit:"8a423691", GitTreeState:"clean", BuildDate:"2024-08-03T08:02:06Z", GoVersion:"go1.22.4", Compiler:"gc", Platform:"linux/amd64"}

    

     Always
    

    1. Get latest oc-mirror
    2.  Follow steps present in the PR here https://github.com/openshift/oc-mirror/pull/883 with the ImageSetConfig given below
    

    When step5 is being performed in (M2D + D2M) i see the issue that is described here.
    

    should not see any issue when trying to use the new release collector for delete feature.
    

    [fedora@preserve-fedora-yinzhou test]$ cat /tmp/clid-99.yaml 
apiVersion: mirror.openshift.io/v2alpha1
kind: ImageSetConfiguration
mirror:
  platform:
    channels:
      - name: stable-4.12
        minVersion: 4.12.61
        maxVersion: 4.12.61
  operators:
  - catalog: oci:///test/ibm-catalog
  - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.15
    packages:
    - name: devworkspace-operator
      minVersion: "0.26.0"
    - name: nfd
      maxVersion: "4.15.0-202402210006"
    - name: cluster-logging
      minVersion: 5.8.3
      maxVersion: 5.8.4
    - name: quay-bridge-operator
      channels:
      - name: stable-3.9
        minVersion: 3.9.5
    - name: quay-operator
      channels:
      - name: stable-3.9
        maxVersion: "3.9.1"
    - name: odf-operator
      channels:
      - name: stable-4.14
        minVersion: "4.14.5-rhodf"
        maxVersion: "4.14.5-rhodf"
  additionalImages:
  - name: registry.redhat.io/ubi8/ubi:latest
  - name: quay.io/openshifttest/hello-openshift@sha256:61b8f5e1a3b5dbd9e2c35fd448dc5106337d7a299873dd3a6f0cd8d4891ecc27
  - name: quay.io/openshifttest/scratch@sha256:b045c6ba28db13704c5cbf51aff3935dbed9a692d508603cc80591d89ab26308