Bug 1812593 - cluster-policy-controller doesn't live reload client certs
Summary: cluster-policy-controller doesn't live reload client certs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-controller-manager
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.5.0
Assignee: Tomáš Nožička
QA Contact: zhou ying
URL:
Whiteboard:
Depends On:
Blocks: 1812594
TreeView+ depends on / blocked
 
Reported: 2020-03-11 16:08 UTC by Tomáš Nožička
Modified: 2020-07-13 17:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1812594 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:19:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-policy-controller pull 19 0 None closed Bug 1812593: Live reload kubeconfig client certs 2021-01-04 22:23:55 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:20:06 UTC

Description Tomáš Nožička 2020-03-11 16:08:50 UTC
Server Version: 4.5.0-0.nightly-2020-03-11-050258

After cert recovery testing QA found the cluster working but saw x509 error in kube-apiserver log.


After cert recovery flow all certs were regenerated but cluster-policy-controller didn't reload new client certificates while kube-controller-manager container did. (share the same kubeconfig.)


must-gather.local.5401326841172208534/quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-237daa2c76ddf92deea9f46b304797e62acfe8c9f76c534a863b1dc4e7ef509e/namespaces/openshift-kube-controller-manager/pods/kube-controller-manager-xxia03-7cblr-m-0.c.openshift-qe.internal/cluster-policy-controller/cluster-policy-controller/logs/current.log:582:2020-03-11T13:04:43.72597951Z E0311 13:04:43.725876       1 leaderelection.go:331] error retrieving resource lock openshift-kube-controller-manager/cluster-policy-controller: Unauthorized

must-gather.local.5401326841172208534/quay-io-openshift-release-dev-ocp-v4-0-art-dev-sha256-237daa2c76ddf92deea9f46b304797e62acfe8c9f76c534a863b1dc4e7ef509e/namespaces/openshift-kube-apiserver/pods/kube-apiserver-xxia03-7cblr-m-0.c.openshift-qe.internal/kube-apiserver/kube-apiserver/logs/current.log:1658:2020-03-11T13:04:43.725314803Z E0311 13:04:43.725256       1 authentication.go:104] Unable to authenticate the request due to an error: x509: certificate has expired or is not yet valid

Comment 3 zhou ying 2020-03-13 10:31:44 UTC
Confirmed with payload: 4.5.0-0.nightly-2020-03-13-001017, the issue has fixed.

Comment 5 errata-xmlrpc 2020-07-13 17:19:39 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


Note You need to log in before you can comment on or make changes to this bug.