Description of problem: The origin-logging-curator is the OCP version v3.9.14, and auth-proxy is fix version v1.0.0. Version-Release number of selected component (if applicable): openshift-ansible:master How reproducible: always Steps to Reproduce: 1. Check the image version $ oc get dc -o yaml |grep image |grep -v imagePullPolicy image: docker.io/openshift/origin-logging-curator:v3.9.14 image: docker.io/openshift/origin-logging-elasticsearch:latest image: docker.io/openshift/oauth-proxy:v1.0.0 image: docker.io/openshift/origin-logging-kibana:latest image: docker.io/openshift/origin-logging-auth-proxy:latest $ oc get ds -o yaml |grep image |grep -v imagePullPolicy image: docker.io/openshift/origin-logging-fluentd:latest Actual Result: The origin-logging-curator image vesion is v3.9.14, and auth-proxy is v1.0.0. Expected Result: The origin-logging-curator image vesion is latest, and auth-proxy is latest. Additional info:
It seems that the approach is not that they should be latest. We shouldn't be setting our image versions to 'latest' by default at all as this can cause issues when customers do not upgrade but instead let the 'latest' image continue to be pulled with redeploys. We have different tags to specify the image versions for logging components and the proxy which should be used instead if we want them all to be 'latest'.
https://github.com/openshift/openshift-ansible/pull/7748
https://github.com/openshift/openshift-ansible/pull/7791
Check the latest code, It will use openshift_image_tag as default image version
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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196