Bug 1668233
Summary: | oc image mirror fails with error 'tag: unexpected end of JSON input' when trying to mirror image from Red Hat registry. | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Mahesh Taru <mtaru> | |
Component: | ImageStreams | Assignee: | Ben Parees <bparees> | |
Status: | CLOSED ERRATA | QA Contact: | XiuJuan Wang <xiuwang> | |
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 3.9.0 | CC: | aos-bugs, bparees, jokerman, mmccomas, wzheng | |
Target Milestone: | --- | |||
Target Release: | 4.1.0 | |||
Hardware: | Unspecified | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: oc image mirror command could not handle metadata coming from the redhat registry
Consequence: images could not be mirrored from that registry this the oc image mirror tool
Fix: metadata handling was updated
Result: images can now be mirrored from the redhat registry
|
Story Points: | --- | |
Clone Of: | ||||
: | 1670551 1676404 (view as bug list) | Environment: | ||
Last Closed: | 2019-06-04 10:42:06 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1670551, 1676404 |
Description
Mahesh Taru
2019-01-22 09:26:37 UTC
This command was experimental in v3.9. The issue w/ mirroring from the redhat registry is being resolved in v4.0, the fix will not be backported since the command was experimental. This cmd works in ocp 4.0 client: oc v4.0.0-0.143.0 server: 4.0.0-0.nightly-2019-01-23-024459 [xiuwang@dhcp-140-96 ~]$ oc image mirror registry.access.redhat.com/openshift3/jenkins-2-rhel7:v3.11 docker.io/xiuwang/jenkins-2-rhel7:v3.11 docker.io/ xiuwang/jenkins-2-rhel7 blobs: registry.access.redhat.com/openshift3/jenkins-2-rhel7 sha256:d134b18b98b0d113b7b1194a60efceaa2c06eff41386d6c14b0e44bfe557eee8 1.194KiB registry.access.redhat.com/openshift3/jenkins-2-rhel7 sha256:e30797a7050fb24792d750b433f63ee2200603447868989f69ea2d17ef06849d 4.568KiB registry.access.redhat.com/openshift3/jenkins-2-rhel7 sha256:ca8b1d3d5d62df1071d4ac27a727690796de5e8554f9f57f98f21da458593b68 7.136MiB registry.access.redhat.com/openshift3/jenkins-2-rhel7 sha256:836b6d169c26dc1bbb677887b271335e9c41713f18d83ae91a04d66bb5ff0188 32.02MiB registry.access.redhat.com/openshift3/jenkins-2-rhel7 sha256:23113ae36f8e9d98b1423e44673979132dec59db2805e473e931d83548b0be82 72.21MiB registry.access.redhat.com/openshift3/jenkins-2-rhel7 sha256:4aa86705ce54f5825010ccb2ae3465d909d4d66dff2834e39b155a52c9b850d2 100.4MiB registry.access.redhat.com/openshift3/jenkins-2-rhel7 sha256:07d56856146dee3dcf38db6769b9b08a09a1352dd40be60c63bec96f20ecea9e 327.5MiB manifests: sha256:9aee6b0423712b4bee3094b315dd42186e6776a4484ec17e20a83ab6f35e9859 -> v3.11 stats: shared=0 unique=7 size=539.3MiB ratio=1.00 phase 0: docker.io xiuwang/jenkins-2-rhel7 blobs=7 mounts=0 manifests=1 shared=0 info: Planning completed in 7.45s uploading: docker.io/library/xiuwang/jenkins-2-rhel7 sha256:07d56856146dee3dcf38db6769b9b08a09a1352dd40be60c63bec96f20ecea9e 327.5MiB uploading: docker.io/library/xiuwang/jenkins-2-rhel7 sha256:4aa86705ce54f5825010ccb2ae3465d909d4d66dff2834e39b155a52c9b850d2 100.4MiB uploading: docker.io/library/xiuwang/jenkins-2-rhel7 sha256:836b6d169c26dc1bbb677887b271335e9c41713f18d83ae91a04d66bb5ff0188 32.02MiB uploading: docker.io/library/xiuwang/jenkins-2-rhel7 sha256:ca8b1d3d5d62df1071d4ac27a727690796de5e8554f9f57f98f21da458593b68 7.136MiB uploading: docker.io/library/xiuwang/jenkins-2-rhel7 sha256:23113ae36f8e9d98b1423e44673979132dec59db2805e473e931d83548b0be82 72.21MiB sha256:9aee6b0423712b4bee3094b315dd42186e6776a4484ec17e20a83ab6f35e9859 docker.io/library/xiuwang/jenkins-2-rhel7:v3.11 info: Mirroring completed in 3m26.62s (2.737MB/s) *** Bug 1676404 has been marked as a duplicate of this bug. *** 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, 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/RHBA-2019:0758 |