Red Hat Bugzilla – Bug 1383275
installer should support user specified "IMAGE_VERSION" for registry console deployment.
Last modified: 2017-07-24 10:11 EDT
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:
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,
Very much related, perhaps even a dupe: https://bugzilla.redhat.com/show_bug.cgi?id=1419493
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.
https://github.com/openshift/openshift-ansible/pull/3317
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.
*** Bug 1393666 has been marked as a duplicate of this bug. ***
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