Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): $ oc version --client Client Version: 4.7.0-0.nightly-2020-11-30-172451 How reproducible: Always Steps to Reproduce: 1. Mirror release image to local registry $ oc adm release mirror --from=registry.svc.ci.openshift.org/ocp/release:4.7.0-0.nightly-2020-11-26-221840 --to=upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release --to-release-image=upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release:4.7.0-0.nightly-2020-11-26-221840 2. 3. Actual results: $ oc adm release mirror --from=registry.svc.ci.openshift.org/ocp/release:4.7.0-0.nightly-2020-11-26-221840 --to=upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release --to-release-image=upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release:4.7.0-0.nightly-2020-11-26-221840 <--snip--> Success Update image: upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release:4.7.0-0.nightly-2020-11-26-221840 Mirror prefix: upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release Mirror prefix: upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release:4.7.0-0.nightly-2020-11-26-221840 To use the new mirrored repository to install, add the following section to the install-config.yaml: imageContentSources: - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: quay.io/openshift-release-dev/ocp-v4.0-art-dev - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: quay.io/openshift-release-dev/ocp-v4.0-art-dev - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: registry.svc.ci.openshift.org/ocp/release - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: registry.svc.ci.openshift.org/ocp/release To use the new mirrored repository for upgrades, use the following to create an ImageContentSourcePolicy: apiVersion: operator.openshift.io/v1alpha1 kind: ImageContentSourcePolicy metadata: name: example spec: repositoryDigestMirrors: - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: quay.io/openshift-release-dev/ocp-v4.0-art-dev - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: quay.io/openshift-release-dev/ocp-v4.0-art-dev - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: registry.svc.ci.openshift.org/ocp/release - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: registry.svc.ci.openshift.org/ocp/release Duplicated lines of imageContentSources/repositoryDigestMirrors is seen. Expected results: To use the new mirrored repository to install, add the following section to the install-config.yaml: imageContentSources: - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: quay.io/openshift-release-dev/ocp-v4.0-art-dev - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: registry.svc.ci.openshift.org/ocp/release To use the new mirrored repository for upgrades, use the following to create an ImageContentSourcePolicy: apiVersion: operator.openshift.io/v1alpha1 kind: ImageContentSourcePolicy metadata: name: example spec: repositoryDigestMirrors: - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: quay.io/openshift-release-dev/ocp-v4.0-art-dev - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: registry.svc.ci.openshift.org/ocp/release Additional info: 1. 4.6 does not have such issue.
Sally, probably a simple de-duplication should be sufficient before printing those.
This bug was introduced with the PR that resolved https://bugzilla.redhat.com/show_bug.cgi?id=1878823, i'll add the de-dupe to resolve this,thanks.
Verified this bug with 4.7.0-0.nightly-2020-12-03-205004, get passed. $ oc adm release mirror --from=registry.svc.ci.openshift.org/ocp/release:4.7 --to=upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release --to-release-image=upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release:4.7 <--snip--> Success Update image: upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release:4.7 Mirror prefix: upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release Mirror prefix: upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release:4.7 To use the new mirrored repository to install, add the following section to the install-config.yaml: imageContentSources: - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: quay.io/openshift-release-dev/ocp-v4.0-art-dev - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: registry.svc.ci.openshift.org/ocp/release To use the new mirrored repository for upgrades, use the following to create an ImageContentSourcePolicy: apiVersion: operator.openshift.io/v1alpha1 kind: ImageContentSourcePolicy metadata: name: example spec: repositoryDigestMirrors: - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: quay.io/openshift-release-dev/ocp-v4.0-art-dev - mirrors: - upshift.mirror-registry.qe.devcluster.openshift.com:5000/ocp/release source: registry.svc.ci.openshift.org/ocp/release
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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-2020:5633