Bug 1651895
| Summary: | Image missing for master team | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zhou ying <yinzhou> |
| Component: | Master | Assignee: | Michal Fojtik <mfojtik> |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | aos-bugs, jokerman, mmccomas, sponnaga |
| Target Milestone: | --- | ||
| 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:41: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
zhou ying
2018-11-21 06:54:09 UTC
Confirmed with latest ocp payload image, all the master team image exist . [root@preserved-yinzhou-rhel-1 0221]# oc adm release info --pullspecs "registry.svc.ci.openshift.org/ocp/release:v4.0" |grep kube-apiserver cluster-kube-apiserver-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0beb0440d84b14c69a941393a77d26774424dbbe580da5119dabade050fe5a32 [root@preserved-yinzhou-rhel-1 0221]# oc adm release info --pullspecs "registry.svc.ci.openshift.org/ocp/release:v4.0" |grep kube-contro cluster-kube-controller-manager-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:93e8151a7a329878927cdf46522e2840d704b4155050e801813283df0bc98170 [root@preserved-yinzhou-rhel-1 0221]# oc adm release info --pullspecs "registry.svc.ci.openshift.org/ocp/release:v4.0" |grep openshift-api cluster-openshift-apiserver-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:93f0a25da63a3a546e8a65c8ad232ad3074e66ee74d9e958e9b3078999ebd32f 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 |