-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.19.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
During the oc mirror from a tar to the quay registry the customer is encountering the below error
~~~~
[Worker] error mirroring image quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0068972abd6f7832be48228f1667187e654d1800a907665b42ad25fb98adf936 error: initializing source docker://localhost:55000/openshift/release:4.19.2-x86_64-csi-driver-nfs: reading manifest 4.19.2-x86_64-csi-driver-nfs in localhost:55000/openshift/release: manifest unknown
~~~
The mirroring to disk worked with out errors.
The imageset they are using
~~~
kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v2alpha1
mirror:
platform:
channels:
- name: stable-4.19
minVersion: 4.19.2
maxVersion: 4.19.2
full: true
graph: true
operators: - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.19
packages: - name: kubevirt-hyperconverged
- name: migration-toolkit-for-virtualization-operator
- name: kubernetes-nmstate-operator
- name: node-healthcheck-operator
- name: fence-agents-remediation-operator
- name: kube-descheduler-operator
- name: node-maintenance-operator
- name: aws-load-balancer-operator
- name: 3scale-operator
- name: node-observability-operator
additionalImages: - name: registry.redhat.io/ubi8/ubi:latest
- name: registry.redhat.io/ubi9/ubi@sha256:20f695d2a91352d4eaa25107535126727b5945bff38ed36a3e59590f495046f0
~~~
The command they are using
~~~
oc mirror -c ImageSetConfiguration --from file:///home/base-image-smaller/ docker://<quay registry url>:8443 --v2 – dest-skip-tls -p 8443 -authfile config.json
~~~
disk to mirror works on a machine connected to the internet but not on an isolated machine.