Bug 1383275

Summary: installer should support user specified "IMAGE_VERSION" for registry console deployment.
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: InstallerAssignee: Andrew Butcher <abutcher>
Status: CLOSED ERRATA QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3.1CC: aos-bugs, jkaur, jokerman, mmccomas, myllynen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
The registry console deployment now allows both the prefix and version to be specified if the user needs to reference an alternate registry or specific version of the console. These values may be configured by setting openshift_cockpit_deployer_prefix='registry.example.com/openshift' and openshift_cockpit_deployer_version='3.5.0' which would result in use of 'registry.example.com/openshift/registry-console:3.5.0'.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-12 18:47:49 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 Johnny Liu 2016-10-10 10:34:48 UTC 
Description of problem:
Check [1], the deploy command does not support user specified "IMAGE_VERSION", while it is supported in [2].

[1]: https://github.com/openshift/openshift-ansible/blob/master/roles/cockpit-ui/tasks/main.yml#L66
[2]: https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_examples/files/examples/v1.3/infrastructure-templates/enterprise/registry-console.yaml#L107

Version-Release number of selected component (if applicable):
openshift-ansible-3.3.30-1.git.0.b260e04.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Johnny Liu 2016-11-08 02:40:15 UTC 
Now registry console 3.4 image is built out, should not we fix this bug in 3.4? If no, that means, in 3.4 install, user would install a 3.3 registry-console,
Comment 2 Marko Myllynen 2017-02-08 10:29:10 UTC 
Very much related, perhaps even a dupe:

https://bugzilla.redhat.com/show_bug.cgi?id=1419493
Comment 3 Scott Dodson 2017-02-08 13:32:26 UTC 
I think requiring the user to specify the version to get the version that matches their environment is incorrect. We should fix both of these and we can do so independently.
Comment 4 Scott Dodson 2017-02-09 19:35:56 UTC 
https://github.com/openshift/openshift-ansible/pull/3317
Comment 6 Johnny Liu 2017-02-10 07:01:29 UTC 
Verified this bug with openshift-ansible-3.5.6-1.git.0.5e6099d.el7.noarch, and PASS.

1. Add the following line into inventory host file:
openshift_cockpit_deployer_prefix=registry.xxx.com/openshift3/
openshift_cockpit_deployer_version=3.4

2. After installation checking:
# oc describe po registry-console-1-nsvb4 |grep Image
    Image:		registry.xxx.com/openshift3/registry-console:3.4
# docker images|grep registry-console
registry.xxx.com/openshift3/registry-console      3.4                 5d0c43da3e17        3 weeks ago         221.3 MB


By default, registry-console 3.5 would be installed by 3.5 installer, after set openshift_cockpit_deployer_version to 3.4, registry-console 3.4 is installed.
Comment 7 Scott Dodson 2017-04-11 17:02:32 UTC 
*** Bug 1393666 has been marked as a duplicate of this bug. ***
Comment 9 errata-xmlrpc 2017-04-12 18:47:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0903