vsphere-csi-node crashloopBackOff due to wrong address

[cleman95]

vSphere Server Info

• vSphere version: 3.3.1

Rancher Server Setup

• Rancher version: v2.10.2 Prime
• Installation option (Docker install/Helm Chart):
  • Helm Chart: rancher-vsphere-csi 3.3.1-rancher8 deployed on rke2

Information about the Cluster

• Kubernetes version: DownStream rke2 cluster imported running Kubernetes 1.31

Describe the bug

When installing the vsphere-csi helm chart, the pods of the vpshere-csi-node daemonset are in a crashloopBackOff state.
The liveness-probe and node-driver-registrar containers are getting a timeout connection to unix:///csi/csi.sock
In the logs I see that vsphere-csi-node container listen for connections on address /csi/csi.sock]

I checked the configuration files from vmware and it seems that in the templates/node/daemonset.yaml the address is missconfigured:

vsphere-charts/charts/rancher-vsphere-csi/templates/node/daemonset.yaml

Line 118 in 52aae72

value: unix:///csi/csi.sock]

If needed, I can open a PR to fix this.

Thanks you in advance

[snasovich]

@cleman95 , thank you for reporting this. Looks like regression caused by inadvertent change here: https://github.com/rancher/vsphere-charts/pull/97/files#diff-020927250b49c781c2630c8592e22dd79ec779494f92faa81c4b7ebe1cb00c24R118

Someone from our team will get this addressed shortly.

[snasovich]

@cleman95 , once again, thank you for reporting this.
I'm actually curious how are you installing this Helm chart as we have not released 3.3.1-rancher8 for use in Rancher Apps, the latest released version for 2.10.x line of Rancher releases is based on 3.3.1-rancher7 and does not have the invalid value (see https://github.com/rancher/charts/blob/release-v2.10/charts/rancher-vsphere-csi/105.0.1%2Bup3.3.1-rancher7/templates/node/daemonset.yaml#L118).

It doesn't change the fact we need to fix it but explains why it wasn't caught in testing yet.

[cleman95]

Hi, I'm installing this Helm Chart by clonning this repo and package it myself not from Rancher Apps. Thank you for the quick fix !