Description of problem: Prometheus images(oauth-proxy, prometheus-alertmanager, message-buffer, prometheus) are not pushed to brew and ops repo Prometheus images are in docker.io repo docker.io/openshift/oauth-proxy v1.0.0 b02dfa547075 8 days ago 231.4 MB docker.io/openshift/prometheus-alertmanager dev d9e0743d1e34 7 weeks ago 220.7 MB docker.io/ilackarms/message-buffer latest cd11cbfa90f6 10 weeks ago 10.58 MB docker.io/openshift/prometheus v2.0.0-dev f809d919b4fd 10 weeks ago 267.6 MB Take message-buffer for example # docker pull brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/message-buffer Using default tag: latest Trying to pull repository brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/message-buffer ... unknown: Not Found # docker pull registry.ops.openshift.com/openshift3/message-buffer Using default tag: latest Trying to pull repository registry.ops.openshift.com/openshift3/message-buffer ... manifest unknown: manifest unknown Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Pull prometheus images from brew and ops repo 2. 3. Actual results: prometheus images are not exist in brew and ops repo Expected results: prometheus images should exist in brew and ops repo Additional info:
Blocks testing on OCP if use images from brew and ops repo, could continue testing with images from docker.io
I see these images available. We just need to ensure that we differentiate between origin and OCP install images. # docker images | grep -e prometheus -e oauth registry.ops.openshift.com/openshift3/oauth-proxy latest 34236c01f126 2 days ago 228.5 MB registry.ops.openshift.com/openshift3/prometheus latest 78a1965a1957 6 days ago 254.4 MB registry.ops.openshift.com/openshift3/prometheus-alert-buffer latest 6cf7333ad173 6 days ago 212 MB registry.ops.openshift.com/openshift3/prometheus-alertmanager latest 63b53de60cff 6 days ago 216.7 MB
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/RHSA-2017:3188