Normal Description of problem:
While trying to perform partially connected mirroring using oc-mirror for OCP 4.13.44 stable channel to internal mirror registry(quay registry), cutomer was getting below error. Same was seen while trying to mirror the OCP version 4.13.44 to local disk.
But, when we tried from our end we could see mirroring worked for us in our lab. Upon checking it is found the reported overlay is not present on the release.txt under OCP version 4.13.44
~~~
./oc-mirror --config=image-config.yaml docker://mirror.xxx.xxx.local:8443
error: error retrieving mapping information for quay.io/openshift-release-dev/ocp-release@sha256:7e85f7274e5a63e604952b9bb6cc03002213541fbcfa8a22e39bebee37e57465: unable to retrieve release image info: unable to iterate over layer sha256:7e85f7274e5a63e604952b9bb6cc03002213541fbcfa8a22e39bebee37e57465 from quay.io/openshift-release-dev/ocp-release@sha256:7e85f7274e5a63e604952b9bb6cc03002213541fbcfa8a22e39bebee37e57465: exit status 3: unpigz: skipping: <stdin>: corrupted -- incomplete deflate data
unpigz: abort: internal threads error
~~~
Imagesetconfi YAML:
~~~
kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v1alpha2
storageConfig:
registry:
imageURL: mirror.xxx.xxx.local:8443/mirror/oc-mirror-metadata
skipTLS: true
mirror
platform:
channels:
- name: stable-4.13
minVersion: '4.13.44'
shortestPath: true
graph: true
helm: {}
~~~
Manual pull using podman also faile at customers environment.
$ podman pull quay.io/openshift-release-dev/ocp-release@sha256:7e85f7274e5a63e604952b9bb6cc03002213541fbcfa8a22e39bebee37e57465
Trying to pull quay.io/openshift-release-dev/ocp-release@sha256:7e85f7274e5a63e604952b9bb6cc03002213541fbcfa8a22e39bebee37e57465...
Error: initializing source docker://quay.io/openshift-release-dev/ocp-release@sha256:7e85f7274e5a63e604952b9bb6cc03002213541fbcfa8a22e39bebee37e57465: reading manifest sha256:7e85f7274e5a63e604952b9bb6cc03002213541fbcfa8a22e39bebee37e57465 in quay.io/openshift-release-dev/ocp-release: manifest unknown
Customer was able to mirror other versions like 4.13.48 and 4.14.35.
Version-Release number of selected component (if applicable):
4.13.44
How reproducible:
Steps to Reproduce:
1. Try to create Imagesetconfig YAML for OCP 4.13.44 stable channel
2. Perform mirroing to mirror registry using oc-mirror
Actual results:
error: error retrieving mapping information for quay.io/openshift-release-dev/ocp-release@sha256:7e85f7274e5a63e604952b9bb6cc03002213541fbcfa8a22e39bebee37e57465: unable to retrieve release image info: unable to iterate over layer sha256:7e85f7274e5a63e604952b9bb6cc03002213541fbcfa8a22e39bebee37e57465 from quay.io/openshift-release-dev/ocp-release@sha256:7e85f7274e5a63e604952b9bb6cc03002213541fbcfa8a22e39bebee37e57465: exit status 3: unpigz: skipping: <stdin>: corrupted -- incomplete deflate data unpigz: abort: internal threads error
Expected results:
Successful Mirroring of OCP version 4.13.44
Additional info:
Upon checking it is found the reported overlay is not present on the release.txt under OCP version 4.13.44
OC-Mirror version (tried both 4.16 and 4.17)
~~~
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:"4.16.0-202406200537.p0.g7c0889f.assembly.stream.el9-7c0889f", GitCommit:"7c0889f4bd343ccaaba5f33b7b861db29b1e5e49", GitTreeState:"clean", BuildDate:"2024-06-20T10:52:05Z", GoVersion:"go1.21.9 (Red Hat 1.21.9-1.module+el8.10.0+21671+b35c3b78) X:strictfipsruntime", Compiler:"gc", Platform:"linux/amd64"}
~~~
Machine is of rhel8 from which oc-mirror command is executed
