Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1391971

Summary:	Don't expose 'latest' metric images on registry.access.redhat.com
Product:	OpenShift Container Platform	Reporter:	Matt Wringe <mwringe>
Component:	Hawkular	Assignee:	Troy Dawson <tdawson>
Status:	CLOSED NOTABUG	QA Contact:	Peng Li <penli>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	aos-bugs
Target Milestone:	---
Target Release:	---
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:	2016-11-04 15:44:27 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 Matt Wringe 2016-11-04 14:13:52 UTC

Description of problem:

We currently have metric images tagged with 'latest' in registry.access.redhat.com.

What is happening is that some users are specifically changing the image version from the one meant for their version of OpenShift to 'latest', which causes a bunch of problems.

If someone is running OCP 3.3 and they are using the 'latest' images, when OCP 3.4 is released they will automatically bring in the version meant for 3.4.

This can cause problems if we are using new functionality in 3.4 which is not available in 3.3.

It also causes problems if we need to update the templates for the new version, but the configurations they are using are meant for the older version.

Running the 'latest' images is not supported, but because they are there some users do end up changing their configuration to this. If we could remove this option by not exposing the 'lastest' images in the registry, then users cannot get into the problems associated with it.

Comment 1 Troy Dawson 2016-11-04 15:44:27 UTC

This is not a tagging issue but a user configuration issue.
If we removed "latest" then more things would break, including those customers because their pulls would fail.

We are encouraging customers to set their version to v<release>, such as v3.2, v3.3 or v3.4.

I'm marking this as closed, not a bug, but my recommendation is documentation.