Yeah, it's a known problem that we've faced with a certain 4.5 version, can't remember which. It was fixed in later versions of oc, so you'll just need to make sure you have latest 4.5 oc, or 4.6 :)
On Sat, Nov 21, 2020 at 6:22 PM Russ Krichevskiy <russ.krichevs...@gmail.com> wrote: > > Got it. I was using older oc client version (4.5) with 4.6 cluster. > > On Sat, Nov 21, 2020 at 12:00 PM > <users-requ...@lists.openshift.redhat.com> 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 <russ.krichevs...@gmail.com> > > To: users <users@lists.openshift.redhat.com> > > Subject: Master node replacement (VMware IPI) > > Message-ID: > > <caohbogyshrz2-eq13fmvbpwfmh837lxcestgzttazj-mp1c...@mail.gmail.com> > > 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 > _______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
