Bug 1690187
| Summary: | Incorrectly named OCP build image baremetal-machine-controller-container | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Clayton Coleman <ccoleman> |
| Component: | Cloud Compute | Assignee: | Steven Hardy <shardy> |
| Status: | CLOSED ERRATA | QA Contact: | Jianwei Hou <jhou> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | agarcial, aos-cloud, eparis, rbryant, xtian, zhsun |
| Target Milestone: | --- | Keywords: | TestBlocker |
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:46:02 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: | |||
|
Description
Clayton Coleman
2019-03-19 00:41:32 UTC
Actually, it is correct in origin (baremetal-machine-controllers. The OCP name must match Origin. https://github.com/openshift/ocp-build-data/blob/openshift-4.0/images/baremetal-machine-controller.yml#L12 verified with oc get istag -nocp | grep 4.0-art-latest:baremetal-machine-controllerß verified clusterversion: 4.1.0-0.nightly-2019-04-22-005054 $ oc adm release info --pullspecs registry.svc.ci.openshift.org/ocp/release:4.1.0-0.nightly-2019-04-22-005054 ... Images: NAME PULL SPEC aws-machine-controllers quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:5fd2900f53d00849b860e57eed7a75e559fe574129befa500b8c876eb757d54a azure-machine-controllers quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:f6e9ba553096a622a15f81840ead9fc0569f7f260ed3005983b78ac3d8a7fc50 baremetal-machine-controllers quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:eca0196c6f968be34f71ebf7b1626d9f89a0f0654859f40e06586c4a375d7fe5 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 |