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.
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.
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).
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.
*** This bug has been marked as a duplicate of bug 1516534 ***