Description of problem: oc-mirror does not validate that the registry in the storage config is accessible. Version-Release number of selected component (if applicable): Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.11.0-202206101306.p0.g01d488f.assembly.stream-01d488f", GitCommit:"01d488f6b1cbab2a199f41ee03d143658605184f", GitTreeState:"clean", BuildDate:"2022-06-10T16:58:35Z", GoVersion:"go1.18", Compiler:"gc", Platform:"linux/amd64"} How reproducible: 100% Steps to Reproduce: 1. Generate a config apiVersion: mirror.openshift.io/v1alpha2 kind: ImageSetConfiguration storageConfig: registry: imageURL: fakeregistry.com/example/oc-mirror skipTLS: true mirror: helm: repositories: - name: podinfo url: https://stefanprodan.github.io/podinfo charts: - name: podinfo version: 5.0.0 2. oc-mirror --config imageset-config.yaml file:// Actual results: oc-mirror mirrors the images and fails at the end when trying to publish the metadata. Expected results: oc-mirror fails because this registry is invalid Additional info: https://github.com/openshift/oc-mirror/issues/249
can't reproduce the issue now: oc-mirror version Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.11.0-202205131159.p0.g7bde4c7.assembly.stream-7bde4c7", GitCommit:"7bde4c7bde6b829a34592b2d12115fb38b15576f", GitTreeState:"clean", BuildDate:"2022-05-13T12:59:14Z", GoVersion:"go1.18", Compiler:"gc", Platform:"linux/amd64"} [root@localhost ocmirrortest]# oc-mirror --config regsitryve.yaml file:// Creating directory: oc-mirror-workspace/src/publish Creating directory: oc-mirror-workspace/src/v2 Creating directory: oc-mirror-workspace/src/charts error: Get "https://fakeregistry.com/v2/": dial tcp: lookup fakeregistry.com: no such host; Get "http://fakeregistry.com/v2/": dial tcp: lookup fakeregistry.com: no such host
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069