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

Bug 1516535

Summary: openshift_image_tag doesn't behave as expected
Product: OpenShift Container Platform Reporter: Erik M Jacobs <ejacobs>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED DUPLICATE QA Contact: Johnny Liu <jialiu>
Severity: urgent Docs Contact:
Priority: high    
Version: 3.7.0CC: aos-bugs, ccoleman, erich, jokerman, mmccomas
Target Milestone: ---   
Target Release: 3.11.0   
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: 2018-06-21 15:09:38 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 Erik M Jacobs 2017-11-22 20:41:13 UTC
hosts.example says:

# Specify an exact container image tag to install or configure.
# WARNING: This value will be used for all hosts in containerized environments, even those that have another version installed.
# This could potentially trigger an upgrade and downtime, so be careful with modifying this value after the cluster is set up.
#openshift_image_tag=v3.7.0

After some conversation, this appears to only affect the containerized image components (master/node/etc) and has no downstream affect on things inside OpenShift (router, etc).

An end user looking at this option would expect that openshift_image_tag would affect all openshift component images.

In reality, this should be what this option does. If that's not the intention of this option, we need to:

* change the name
* change the description

And then we should implement an image_tag option that actually does what would be expected of this.

Comment 1 Scott Dodson 2017-11-22 21:39:38 UTC
Eric (Rich), 

By what assessment have you arrived at this being urgent? It's been like this ever since containerized installation was introduced in 3.1.

Comment 3 Clayton Coleman 2018-03-26 03:33:43 UTC
A number of changes have landed in 3.10 to make this more consistent.  https://github.com/openshift/openshift-ansible/pull/7645 has some of the beginning of consolidation around oreg_url which is required in order to make publishing via CI jobs feasible.  There have been significant changes to image_tag already, and by 3.10 we should be in a spot where only openshift_release must be specified for the majority of consumers (due to the use of rolling tags in some areas).

Comment 4 Scott Dodson 2018-06-21 13:35:17 UTC
openshift_version and oreg_url implementation have been completely refactored in 3.10. This should be marked as a dupe of the bug where we worked on that.

Comment 5 Scott Dodson 2018-06-21 15:09:38 UTC

*** This bug has been marked as a duplicate of bug 1516534 ***