Jing Xu

Similar issue opened before https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/1661

which component register "register the CsiNodeTopology CRD"? how to make sure CRD successfully registered before CSI node daemonset pod to create the instance?

Please see more logs https://gist.github.com/jingxu97/cc013868270f4d05497a7aba2b59221c From what I searched, some logic related to discover VM and register does not have a retry logic, and causing the following VM not found...

> > how to make sure CRD successfully registered before CSI node daemonset pod to create the instance? > > you can install the CSI controller Pod first, let all...

Our CI tests start have the same failures often now. I checked the kb article, but there is not Resolution yet. The workaround is to Restart vsan-health service. But this...

Re https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/2165#issuecomment-1490788517, the problem is CSI migration is normally performed during cluster upgrade, when the node drain happened. So we cannot make sure FCD is registered before node drain starts....

@divyenpatel Is there a manual workaround without updating to the vsphere new versions?

@divyenpatel I searched up on 7.0p07, it looks like mapping to build 21424296 https://packages.vmware.com/tools/versions But the build was published 2023/03/30 according to https://kb.vmware.com/s/article/2143832. Could you please help double check this...

@xing-yang @divyenpatel Could you help reopen this issue? @jrife could help follow up on this.

/cc @xing-yang @divyenpatel