Hide Forgot
Description of problem: Found only "machine-os-content" image is from registry.svc.ci.openshift.org, other components are from quay.io. Version-Release number of selected component (if applicable): 4.0.0-0.nightly-2019-03-19-004004 How reproducible: Always Steps to Reproduce: 1. Install a cluster using 4.0.0-0.nightly-2019-03-19-004004 payload 2. Check all images in this payload image 3. Actual results: oc adm release info --pullspecs Name: 4.0.0-0.nightly-2019-03-19-004004 Digest: sha256:5535717a5cabb2c5587567a5c32d35e4d8ac238e9459a6ffe14c789b42ac5cc2 Created: 2019-03-18 20:41:54 -0400 EDT OS/Arch: linux/amd64 Manifests: 258 Release Metadata: Version: 4.0.0-0.nightly-2019-03-19-004004 Upgrades: <none> Component Versions: Kubernetes 1.12.4 Images: NAME PULL SPEC <--snp--> machine-os-content registry.svc.ci.openshift.org/ocp/4.0-art-latest-2019-03-19-004004@sha256:65406dd82ead5a7cc6bd34f9c8e49b6212a7ab1db9cc9d33ba14613719e3771f <--snp--> Found only "machine-os-content" image is from registry.svc.ci.openshift.org, other components are from quay.io. Expected results: "machine-os-content" should keep consistent with others. Additional info:
This is not a bug, but how nightly builds are created. The presence of a registry.svc.ci image in a release published to quay would be a bug.
*** Bug 1669962 has been marked as a duplicate of this bug. ***
This is already fixed. The promote job now sets the correct URL.
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