Re: Master node replacement (VMware IPI)
> On Nov 21, 2020, at 10:54 AM, Russ Krichevskiy > 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
Re: users Digest, Vol 100, Issue 10
Got it. I was using older oc client version (4.5) with 4.6 cluster. On Sat, Nov 21, 2020 at 12:00 PM wrote: > > Send users mailing list submissions to > users@lists.openshift.redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > or, via email, send a message with subject or body 'help' to > users-requ...@lists.openshift.redhat.com > > You can reach the person managing the list at > users-ow...@lists.openshift.redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > >1. Master node replacement (VMware IPI) (Russ Krichevskiy) > > > -- > > Message: 1 > Date: Sat, 21 Nov 2020 10:54:17 -0500 > From: Russ Krichevskiy > To: users > Subject: Master node replacement (VMware IPI) > Message-ID: > > Content-Type: text/plain; charset="UTF-8" > > 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" > > Any pointers? > > > > -- > > ___ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > > End of users Digest, Vol 100, Issue 10 > ** > ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Master node replacement (VMware IPI)
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" Any pointers? ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
