Bug 1810008 - [UPI]Failed to recovery from expired certificates with all nodes "NotReady"
Summary: [UPI]Failed to recovery from expired certificates with all nodes "NotReady"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.5.0
Assignee: Tomáš Nožička
QA Contact: Xingxing Xia
URL:
Whiteboard:
: 1805398 (view as bug list)
Depends On: 1811061
Blocks: 1771410
TreeView+ depends on / blocked
 
Reported: 2020-03-04 11:54 UTC by Tomáš Nožička
Modified: 2020-07-13 17:18 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1771410
Environment:
Last Closed: 2020-07-13 17:17:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-apiserver-operator pull 785 0 None closed Bug 1810008: Use the new tls-server-name option in kubeconfig 2020-12-11 10:37:16 UTC
Github openshift cluster-kube-controller-manager-operator pull 356 0 None closed Bug 1810008: Use the new tls-server-name option in kubeconfig 2020-12-11 10:37:16 UTC
Github openshift cluster-kube-controller-manager-operator pull 361 0 None closed Bug 1810008: Reload client certs 2020-12-11 10:37:16 UTC
Github openshift cluster-kube-scheduler-operator pull 216 0 None closed Bug 1810008: Add cert syncer 2020-12-11 10:37:16 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:18:17 UTC

Comment 4 Xingxing Xia 2020-03-11 10:57:42 UTC
Verified in 4.5.0-0.nightly-2020-03-11-050258 upi on gcp env, after breaking the cluster per above google document, wait for cert expired, then re-start masters, clusters can come back well, control plane certs can recover automatically, oc get po/co/no and other oc basic operations have no problem.

Comment 5 Xingxing Xia 2020-03-20 02:40:49 UTC
*** Bug 1805398 has been marked as a duplicate of this bug. ***

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