Bug 1826885

Summary:	DNS kube-rbac-proxy image not updated during cluster upgrades
Product:	OpenShift Container Platform	Reporter:	Stephen Greene <sgreene>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	DNS	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aos-bugs
Version:	4.5
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:30:21 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 Stephen Greene 2020-04-22 17:05:01 UTC

Description of problem:
The cluster coreDNS Daemonset update function does not iterate over the "kube-rbac-proxy" image reference when updating the container images in the daemonset. 

Version-Release number of selected component (if applicable):
4.5

How reproducible:


Steps to Reproduce:
1.Start a 4.5 cluster
2.Update to newer 4.x cluster version with a newer version of "kube-rbac-proxy"

Actual results:
"kube-rbac-proxy" image reference won't be update to the correct version.

Expected results:
"kube-rbac-proxy" is updated.


Additional info:

Comment 4 Hongan Li 2020-04-26 09:58:27 UTC

Upgrade from 4.5.0-0.nightly-2020-04-21-103613 to 4.5.0-0.nightly-2020-04-25-17044 and the KUBE_RBAC_PROXY_IMAGE is updated after upgrade.

before upgrade:
KUBE_RBAC_PROXY_IMAGE=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:80328072c0dd75fb3e207e07dd1374e999c2f7da7104e707f87a0bd83f7ac5d5

after upgrade:
KUBE_RBAC_PROXY_IMAGE=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c09411a27f0627e1eabf82d6e607b282e81154bd64db90dc0a4347fa4f1a637b

Comment 5 errata-xmlrpc 2020-07-13 17:30:21 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-2020:2409