Closed nicosto closed 2 weeks ago
Additional tests: This is failing with vsphere 6.7.0 build 16709110 Working in vsphere 8.0.3 build 24091160
falling in vsphere 8.0.2 with vsan storage
NAME READY STATUS RESTARTS AGE vsphere-csi-controller-5cdfcf4ff9-qs6dv 5/7 ImagePullBackOff 0 2m47s vsphere-csi-controller-5cdfcf4ff9-vpkqw 5/7 ImagePullBackOff 0 2m47s vsphere-csi-controller-5cdfcf4ff9-xtn2k 5/7 ImagePullBackOff 0 2m47s vsphere-csi-node-chw9v 1/3 CrashLoopBackOff 4 (16s ago) 2m47s vsphere-csi-node-m9r99 1/3 CrashLoopBackOff 4 (17s ago) 2m47s vsphere-csi-node-r78bn 1/3 CrashLoopBackOff 4 (17s ago) 2m47s vsphere-csi-node-rq2bm 1/3 CrashLoopBackOff 4 (17s ago) 2m47s vsphere-csi-node-zdhtj 1/3 CrashLoopBackOff 4 (17s ago) 2m47s
@nicosto @chandu3377 Please refer to https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/3000
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
csi controller crash with an error related to vSAN. Using default settings to use vmdk based storage as no vSAN is installed.
What can trigger the request of vSAN support during deployment?
What you expected to happen:
csi controller running
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
uname -a
): Linux oss-k8s-dev-w230.xxx.xxx.xxx 5.14.0-427.13.1.el9_4.x86_64 #1 SMP PREEMPT_DYNAMIC Wed May 1 19:11:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux