Closed DanielFroehlich closed 2 years ago
Heads up @cluster/ocp4-admin - the "cluster/ocp4" label was applied to this issue.
@Javatar81 would you be able to take a look?
Please check if it is the same as https://github.com/stormshift/support/issues/46
control-1 (NotReady):
[core@control-1 ~]$ systemctl status kubelet
Apr 13 09:38:33 control-1.ocp4.stormshift.coe.muc.redhat.com hyperkube[126009]: I0413 09:38:33.812969 126009 csi_plugin.go:1031] Failed to contact API server when waiting for CSINode publishing: csinodes.storage.k8s.io "control-1.ocp4.stormshift.coe.muc.redhat.com" is forbidden: User "system:anonymous" cannot get resource "csinodes" in API g>
Apr 13 09:38:33 control-1.ocp4.stormshift.coe.muc.redhat.com hyperkube[126009]: E0413 09:38:33.907551 126009 kubelet.go:2303] "Error getting node" err="node \"control-1.ocp4.stormshift.coe.muc.redhat.com\" not found"
Identified problem with Kubelets not working. Followed these docs
systemctl status kubelet
found kubelet.go:2303] "Error getting node" err="node \"[control-1.ocp4.stormshift.coe.muc.redhat.com](http://control-1.ocp4.stormshift.coe.muc.redhat.com/)\" not found"
Recovering as described in this issue: https://github.com/stormshift/support/issues/72
Approved CSRs and enabled scheduling
All nodes are ready
LGTM, THX
OCP4 Cluster is in INOP state after rebuild, login not working etc. Looks like we have lost quorum, too many not ready nodes:
I suspect cert issue due to long days offline. I did approve CSR in state pending, but that did not help. We need to invistigate and probably recover from expirired certs. We had this issue already, please search here for the resulotion.