Manual clone of https://bugzilla.redhat.com/show_bug.cgi?id=1759523 (see https://bugzilla.redhat.com/show_bug.cgi?id=1759523#c25 for rationale).
Description of problem:
After successful install of ocp 4.2 and waiting some amount of time we can nolong login to the cluster, from browswer or oc command line. Would like to know if there is a way to recover. At the moment I need to destroy my cluster and rebuild it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.wait 24 hours or less
3.then try to login
oc login -u kubeadmin -p <redacted> https://api.simple-sunfish.purple-chesterfield.com:6443
This is intermittent, 1 out of 3 clusters has hit this issue.
*** Bug 1769247 has been marked as a duplicate of this bug. ***
Use the certificate based admin.kubeconfig to run must-gather so we have a point to start debugging from. Also, did these cluster-admins ever manually modify any configmap in `openshift-config-managed`? For a while there were some bad directions in a KCS article that resulted in corrupting some trust bundles.