> On Nov 21, 2020, at 10:54 AM, Russ Krichevskiy <russ.krichevs...@gmail.com> > wrote: > > I am trying to replace a failed master node that did not reboot > properly during upgrade (4.6.3 to 4.6.4). > Referencing documentation here > https://docs.openshift.com/container-platform/4.6/backup_and_restore/replacing-unhealthy-etcd-member.html#restore-replace-stopped-etcd-member_replacing-unhealthy-etcd-member. > Deleted etcd member and machine config; brought up a new node and I > see it rebooted. I added its new VSphereMachineProviderSpec and it > shows up as provisioned in openshift-machine-api. However, it will not > progress any further and will not join. > > csr-zfdkh 8h kubernetes.io/kube-apiserver-client-kubelet > system:serviceaccount:openshift-machine-config-operator:node-bootstrapper > Pending > > $ oc adm certificate approve csr-zfdkh > No resources found > error: no kind "CertificateSigningRequest" is registered for version > "certificates.k8s.io/v1" in scheme > "k8s.io/kubectl/pkg/scheme/scheme.go:28"
What version of oc is this? Generally this shouldn’t happen unless something is catastrophically wrong (old client, corrupted local cache of resources, connected to wrong kube-apiserver, or control plane broken in ways it cannot be broken anymore). > > Any pointers? > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > _______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
