Bug 1830364

Summary:	Resource Graph is Built Using Legacy Router CA ConfigMap
Product:	OpenShift Container Platform	Reporter:	Daneyon Hansen <dhansen>
Component:	kube-controller-manager	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED ERRATA	QA Contact:	zhou ying <yinzhou>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	aos-bugs, mfojtik
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1833128 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:34:13 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:
Bug Depends On:
Bug Blocks:	1833125, 1833128, 1833130

Description Daneyon Hansen 2020-05-01 18:18:52 UTC

Description of problem:
kube-controller-manager uses the legacy cm/router-ca -n openshift-config-managed to build its resource graph. However, the targetconfig controller uses the new cm/default-ingress-cert -n openshift-config-managed resource to build cm/serviceaccount-ca -n openshift-kube-controller-manager.

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

How reproducible:
Always

Steps to Reproduce:
1. N/A

Actual results:
N/A

Expected results:
N/A

Additional info:
[1] updated the targetconfig controller but did not update the resource graph.


[1] https://github.com/openshift/cluster-kube-controller-manager-operator/pull/402

Comment 3 zhou ying 2020-05-08 07:17:20 UTC

Compared payload: 4.5.0-0.nightly-2020-05-06-003431 with payload: 4.4.0-0.nightly-2020-05-08-004736, the issue has fixed:

oc exec po/kube-controller-manager-operator-xxx cluster-kube-controller-manager-operator resource-graph  |dot -Tpng >output4.png

Comment 4 errata-xmlrpc 2020-07-13 17:34:13 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