Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1561882

Summary: The curator and oauth-proxy image version should be latest
Product: OpenShift Container Platform Reporter: Anping Li <anli>
Component: LoggingAssignee: ewolinet
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: aos-bugs, eparis, rmeggins
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 15:54:19 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 Anping Li 2018-03-29 06:10:31 UTC
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:

Comment 1 ewolinet 2018-03-29 20:43:16 UTC
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'.

Comment 7 Anping Li 2018-07-10 07:26:53 UTC
Check the latest code, It will use openshift_image_tag as default image version

Comment 10 errata-xmlrpc 2020-10-27 15:54:19 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 (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