Description of problem: When openshift_logging_elasticsearch_proxy_image_prefix is not set and openshift_logging_image_prefix is set in inventory. openshift_logging_elasticsearch_proxy_image_prefix should inherit from openshift_logging_image_prefix rather than use the default values in playbook(vars/openshift-enterprise.yml or vars/default_images.yml). The openshift_logging_elasticsearch_proxy_image_prefix should following same rule as openshift_logging_elasticsearch_image_prefix. When openshift_logging_elasticsearch_proxy_image_prefix is not set in inventory file. if openshift_logging_image_prefix is set, it use the value of openshift_logging_image_prefix. When both openshift_logging_elasticsearch_proxy_image_prefix and openshift_logging_image_prefix are not set, it use the default value from playbook. Version-Release number of the following components: logging-fluentd:v3.7.0-0.174.0.0 How reproducible: always Steps to Reproduce: 1. set openshift_logging_image_prefix, and don't set openshift_logging_elasticsearch_proxy_image_prefix. and then deploy logging with playbook openshift_logging_install_logging=true openshift_logging_image_prefix=brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ #openshift_logging_elasticsearch_proxy_image_prefix=brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ 2. Check the image in logging_elasticsearch deployment configure oc get dc logging-es-data-master-31ew93jf -o yaml |grep image Actual results: The logging-es-data-master is using image registry.access.redhat.com/openshift3/oauth-proxy:v3.7 # oc get dc logging-es-data-master-31ew93jf -o yaml |grep image image: registry.access.redhat.com/openshift3/oauth-proxy:v3.7 image: brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-elasticsearch:v3.7 Expected results: The logging-es-data-master is brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/logging-elasticsearch:v3.7 Additional info: You can add openshift_logging_elasticsearch_proxy_image_prefix=brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/
@scott, @jcantril, In v3.7, openshift3/oauth-proxy:v3.7 must be used. QE think it is better to fix it in v3.7.
At the moment, we don't have images tagged appropriately in our upstream registry to be able to follow the convention the other images have [1] I think it is best for oauth-proxy to have its independent versioning at the moment and once we resolve our upstream image issues, then make it consistent with other images. [1] https://hub.docker.com/r/openshift/oauth-proxy/tags/
@Jan, OK, I will use openshift_logging_elasticsearch_proxy_image_prefix and openshift_logging_elasticsearch_proxy_image_version before this bug is fixed.
This seems nice to have rather than a 3.7.0 blocker. Moving to 3.8.0.
Works on openshift-ansible-3.9.0-0.13.0
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-2018:0489