Bug 1492545 – Prometheus images are not pushed to brew and ops repo

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1492545 - Prometheus images are not pushed to brew and ops repo

Summary:	Prometheus images are not pushed to brew and ops repo

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	3.7.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	---
Target Release:	3.7.0
Assigned To:	Zohar Gal-Or
QA Contact:	Johnny Liu
Docs Contact:

URL:
Whiteboard:
Keywords:	TestBlocker

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-09-18 02:23 EDT by Junqi Zhao
Modified:	2017-11-28 17:10 EST (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-11-28 17:10:58 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:3188	normal	SHIPPED_LIVE	Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update	2017-11-28 21:34:54 EST

Groups: None (edit)

Description Junqi Zhao 2017-09-18 02:23:19 EDT

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:

Comment 1 Junqi Zhao 2017-09-18 02:45:31 EDT

Blocks testing on OCP if use images from brew and ops repo, could continue testing with images from docker.io

Comment 2 Scott Dodson 2017-09-18 09:06:40 EDT

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

Comment 7 errata-xmlrpc 2017-11-28 17:10:58 EST

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

Note You need to log in before you can comment on or make changes to this bug.