Bug 1480443 - Clarify and fix the latest tag usage
Summary: Clarify and fix the latest tag usage
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.6.z
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-11 06:29 UTC by Marko Myllynen
Modified: 2017-08-17 14:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-17 14:18:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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