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

Bug 1480443

Summary:	Clarify and fix the latest tag usage
Product:	OpenShift Container Platform	Reporter:	Marko Myllynen <myllynen>
Component:	Installer	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED NOTABUG	QA Contact:	Johnny Liu <jialiu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	3.6.z
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:	2017-08-17 14:18:47 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 Marko Myllynen 2017-08-11 06:29:34 UTC

Description of problem:
In https://bugzilla.redhat.com/show_bug.cgi?id=1443588 it was stated:

latest - as well as no tag (which defaults to latest) :
**Users and scripts should not use the latest tag when dealing with openshift images**

However, in https://bugzilla.redhat.com/show_bug.cgi?id=1479204 and https://bugzilla.redhat.com/show_bug.cgi?id=1480442 we see "latest" being used.

So it would look like our documentation and tools are not consistent.

I'm filing this BZ as a higher level tracker for discussion whether we scripts or docs should be fixed but currently the situation is a bit confusing. Thanks.

Comment 1 Scott Dodson 2017-08-14 15:28:31 UTC

Yes we should avoid using latest. If there are other situations where that's used lets make sure there are bugs on each case.