Bug 1677232
| Summary: | oauth-proxy and grafana uses origin images may bring CreateContainerError on OCP, should use OCP images | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
| Component: | Monitoring | Assignee: | Frederic Branczyk <fbranczy> |
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | mloibl, surbania |
| Target Milestone: | --- | Keywords: | Regression |
| 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:44:00 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
Junqi Zhao
2019-02-14 10:24:18 UTC
As of https://github.com/openshift/cluster-monitoring-operator/pull/259 this should be fixed. Checked 0000_70_cluster-monitoring-operator_04-deployment.yaml in payload, oauth-proxy and grafana use OCP images now
- "-images=prometheus-operator=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:95a1b9562f4377026a659feb9d025af659761e48be1a68b286c761883caf9f2b"
- "-images=prometheus-config-reloader=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:551fc7a7ea1bddab0646b9dac22e04b6597489d0788ae6053f9f6dfc715f0b69"
- "-images=configmap-reloader=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:2c0d8efc722097f4476c9d62d19d54a9061fc7168a432da523c3cda12d144680"
- "-images=prometheus=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:cd698743e1478cf580e2e75749b2c10f7824ffddcee0469dccfaa2f58df2f008"
- "-images=alertmanager=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:7147815b797ba173b494c4d8f468f5bad5231a3f54bdb02960b5cd8f78514d43"
- "-images=grafana=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:51166898d56ed1beacb24bffb4224bd58eedf1d4109fcf74491c2730844724ad"
- "-images=oauth-proxy=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c0dbc2a74a1573bb7a9032ba3ba31fb14c9d575a5483e3cd86baa602568ffc25"
- "-images=node-exporter=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8d3e99a8bc1759788e11dbe9588b6b2cb4976cb2d92f3dc9c6bfadafd549a98c"
- "-images=kube-state-metrics=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:39c22c66cce390d747d116752c1dcc85ff5a9e70587a0649d43b46f017e62948"
- "-images=kube-rbac-proxy=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3a85cf9c98cba46dd4a8cd90c45232fc92c6b3fe3d8d5c3c2efc0084ea3f048f"
- "-images=telemeter-client=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:cdee0fbdfb7f64ee81a543bdad68e77fcaa85f9c4e296ab6cfcb18fe05f12632"
- "-images=prom-label-proxy=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:bceec206dc589dd7d4b499b271027d0f5a06687901db3da3076faeab355b1ee9"
- "-images=k8s-prometheus-adapter=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:f4ae9936c3d4c7ae1854497275e7596109bc60362811cb4771e3392df6b680c5"
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.0.0-0.nightly-2019-02-25-194625 True False 18m Cluster version is 4.0.0-0.nightly-2019-02-25-194625
RHCOS build: 47.330
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 |