Description of problem: If I try to oc mirror to a local storage, oc gets an 404 error for registry.redhat.io/rhel9-beta/tang-operator-bundle and registry.redhat.io/rhel9-beta/tang-operator Version-Release number of selected component (if applicable): oc version: Client Version: 4.10.0-202205120735.p0.g04ad1b5.assembly.stream-04ad1b5 oc mirror version: Client Version: version.Info{Major:"0", Minor:"1", GitVersion:"v0.1.0", GitCommit:"5a749efd3ed6d6e89047fddb5e76d3c0c4fcdff0", GitTreeState:"clean", BuildDate:"2022-05-12T08:54:10Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"} ocp channel: stable-4.10 Steps to Reproduce: 1. Create sample .yaml config: "apiVersion: mirror.openshift.io/v1alpha1 kind: ImageSetConfiguration archiveSize: 4 storageConfig: local: path: /home/shadowman/workspace/mirror/files mirror: ocp: channels: - name: stable-4.10 operators: - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.10" 2. run oc mirror like: "oc mirror --config=sample.yaml file:///home/shadowman/workspace/mirror/files/" Actual results: Fails with error because registry.redhat.io/rhel9-beta/tang-operator-bundle and registry.redhat.io/rhel9-beta/tang-operator are not found: "error: unable to retrieve source image registry.redhat.io/rhel9-beta/tang-operator-bundle manifest sha256:be7053361e3a0e2639b4f4e242aca4ed28aa467f41273ee303228e159d0fef04: error parsing HTTP 404 response body: invalid character 'N' looking for beginning of value: "Not found\n" error: unable to retrieve source image registry.redhat.io/rhel9-beta/tang-operator manifest sha256:9963167fe37897473167d5b1af578881592479093e086d2ffb7ff4b7bec4d39e: error parsing HTTP 404 response body: invalid character 'N' looking for beginning of value: "Not found\n" error mirroring image: an error occurred during planning error: image "registry.redhat.io/3scale-amp2/3scale-rhel7-operator-metadata@sha256:2b709b801c9d28b16e6dd3a4c4b1c529d03b07e51cca2556e4f9b6ab7c8248e4" is invalid or does not exist" Expected results: find all images and succeed without error. Additional info: I can pull via podman this one fine: "podman pull registry.redhat.io/3scale-amp2/3scale-rhel7-operator-metadata@sha256:2b709b801c9d28b16e6dd3a4c4b1c529d03b07e51cca2556e4f9b6ab7c8248e4" But not "registry.redhat.io/rhel9-beta/tang-operator-bundle" and "registry.redhat.io/rhel9-beta/tang-operator-bundle"
The issue here is that the catalog contains the tang-operator.v0.0.24 bundle which includes in its `relatedImages` section two image references which aren't resolvable (404 error). I suspect that the catalog team would need to resolve this. Since this is related to "registry.redhat.io/redhat/redhat-operator-index:v4.10" I suspect that a sub-component of OperatorHub isn't the best, so I'm inquiring where to send this ticket to get you some relief.
This is a catalog issue, and they don't watch this space. We opened https://issues.redhat.com/browse/OCPBUGS-1611 to effort this change. We will close this ticket as WONTFIX since OLM team can't fix this. Please watch the new ticket for issue lifecycle. I've endeavored to add folks as watchers of that issue to help out.
My mistake. Correct project is CLOUDDST. Moved the jira to the right place now: https://issues.redhat.com/browse/CLOUDDST-15715
Got wires crossed on unrelated issues. Third time's the charm? Ticket should be https://issues.redhat.com/browse/CLOUDDST-15717 for follow-up. Apologies for the confusion.
Getting full-circle here.... cloud distribution team says that the operator was EOL by explicit request 14Jun2022 jira: RCMAUTO-5665.