https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# vsphere
a
This message was deleted.
s
Have configured below details in the manifests - csi and cpi -> valuesContent: |- vCenter: host: "xyz" datacenters: "xyz_Datacenter" username: "administrator@vsphere.local" password: "xyz" clusterId: "xyz_Cluster" csiController: nodeSelector: node-role.kubernetes.io/control-plane: "true" csiResizer: enabled: false storageClass: enabled: true name: vsphere-csi-sc isDefault: true
h
You should review logs of 
vsphere-cpi-cloud-controller-manager
a
It looks like your indent is a bit off (but that may be Slack messing up the formatting). Also, you’re missing a reference to a configSecret and maybe port security (if you are using a self-signed certificate for vCenter). csiResizer is disabled by default in our CSI Helm chart, so you can get rid of that entry, too, if you want. i.e:
Copy code
vCenter:
    host: "xyz"
    port: 443
    insecureFlag: "1"
    datacenters: "xyz_Datacenter"
    username: "administrator@vsphere.local"
    password: "xyz"
    configSecret:
      name: "vsphere-config-secret"
      generate: true
  csiController:
    nodeSelector:
      <http://node-role.kubernetes.io/worker|node-role.kubernetes.io/worker>: 'true'
  storageClass:
    datastoreURL: "<ds://xyz_Datastore/>"
    enabled: true
    isDefault: true
s
@adventurous-battery-36116 thanks for the details.. have applied the config as suggested.. could see that the datastoreurl is picked in the logs.. still we are facing the same error..
{"level":"info","time":"2023-08-01T165100.503337287Z","caller":"vanilla/controller.go:1805","msg":"CreateVolume: called with args {Name:pvc-0dafdc33-2b02-44b4-ba0e-820d7e8f5b43 CapacityRangerequired bytes8589934592 VolumeCapabilities[mount<fs_type:\"ext4\" > access_mode&lt;modeMULTI_NODE_MULTI_WRITER > ] Parametersmap[datastoreURLds:///vmfs/volumes/63cf8ece-84187c8e-1397-00215a9b5638/] Secrets:map[] VolumeContentSource:<nil> AccessibilityRequirements:<nil> XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}","TraceId":"1ac5c093-a706-4777-b120-1c3c8e40aea7"} panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x1b22a25] goroutine 305 [running]: sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/vanilla.(*controller).createFileVolume(0xc000222730, {0x26af658, 0xc00074bc20}, 0xc0004665b0) /build/pkg/csi/service/vanilla/controller.go:1736 +0xd05 sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/vanilla.(*controller).CreateVolume.func1() /build/pkg/csi/service/vanilla/controller.go:1848 +0x3d7
@hundreds-evening-84071 there are no errors in the vsphere-cpi-cloud-controller-manager logs.. it was able to connect to the vcenter..
enabled DEVELOPMENT logging level and here are the details.. 
2023-08-01T18:03:10.421Z        INFO    vanilla/controller.go:1805      CreateVolume: called with args {Name:pvc-0dafdc33-2b02-44b4-ba0e-820d7e8f5b43 CapacityRange:required_bytes:8589934592  VolumeCapabilities:[mount:<fs_type:"ext4" > access_mode:<mode:MULTI_NODE_MULTI_WRITER > ] Parameters:map[datastoreURL:ds:///vmfs/volumes/63cf8ece-84187c8e-1397-00215a9b5638/] Secrets:map[] VolumeContentSource:<nil> AccessibilityRequirements:<nil> XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}        {"TraceId": "a326fa60-fee0-4f8f-8a57-ae8db80b086e"}
2023-08-01T180310.421Z DEBUG vsphere/utils.go:522 Checking if vCenter version is of vsan 67u3 release {"TraceId": "a326fa60-fee0-4f8f-8a57-ae8db80b086e"} 2023-08-01T180310.421Z DEBUG vsphere/utils.go:528 vCenter version is :"reserved" {"TraceId": "a326fa60-fee0-4f8f-8a57-ae8db80b086e"} 2023-08-01T180310.421Z DEBUG vanilla/controller.go:1628 Checking if vCenter task for file volume pvc-0dafdc33-2b02-44b4-ba0e-820d7e8f5b43 is already registered. {"TraceId": "a326fa60-fee0-4f8f-8a57-ae8db80b086e"} 2023-08-01T180310.421Z DEBUG cnsvolumeoperationrequest/cnsvolumeoperationrequest.go:141 Getting CnsVolumeOperationRequest instance with name kube-system/pvc-0dafdc33-2b02-44b4-ba0e-820d7e8f5b43 {"TraceId": "a326fa60-fee0-4f8f-8a57-ae8db80b086e"} 2023-08-01T180310.425Z DEBUG vanilla/controller.go:1648 CreateVolume task details for file volume pvc-0dafdc33-2b02-44b4-ba0e-820d7e8f5b43 are not found. {"TraceId": "a326fa60-fee0-4f8f-8a57-ae8db80b086e"} panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x1b22a25] goroutine 265 [running]: sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/vanilla.(*controller).createFileVolume(0xc0001b2af0, {0x26af658, 0xc000909410}, 0xc0006181c0) /build/pkg/csi/service/vanilla/controller.go:1736 +0xd05
a
Are you trying to use RWX volumes?
s
ah yes.. updated to RWO and it worked! Thanks a lot 🙂
so is this already known issue? if someone tries to claim RWX by mistake it crashes the vsphere controller pods?
a
No open/current issues I can see. Closest I could find to what you’re experiencing: https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/2127 And there is a (stale) feature request for RWX: https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/1885
đź‘Ť 1
22 Views
Open in Slack
PreviousNext
Powered by