Open
Description
Describe the bug
Hello,
with version 1.3.0 the cloud-director-named-disk-csi-driver does not work.
- daemonsets.apps => csi-vcd-nodeplugin
- deployments.apps => csi-vcd-controllerplugin
error :
Usage:
/opt/vcloud/bin/cloud-director-named-disk-csi-driver [flags]
Flags:
--cloud-config string CSI driver cloud config
--endpoint string CSI endpoint
-h, --help help for /opt/vcloud/bin/cloud-director-named-disk-csi-driver
--nodeid string node id
--upgrade-rde CSI upgrade rde
-v, --version version for /opt/vcloud/bin/cloud-director-named-disk-csi-driver
panic: error in executing command: [unknown flag: --v]
goroutine 1 [running]:
main.main()
/build/mts/release/bora-23441257/cayman_cloud-director-named-disk-csi-driver/cloud-director-named-disk-csi-driver/src/cmd/csi/main.go:88 +0x285
the --v=5
option is no longer valid.
cf:
- https://github.com/vmware/cloud-director-named-disk-csi-driver/blob/1.6.0/manifests/csi-node-crs.yaml#L96
- https://github.com/vmware/cloud-director-named-disk-csi-driver/blob/1.6.0/manifests/csi-node-crs.yaml.template#L94
Reproduction steps
- Create CAPVCD cluster. v1.3.0
- Deploy VCD CSI.
- Create StorageClass. (with csi.cloud-director.vmware.com)
Expected behavior
Deploy VCD CSI whitout error.
delete the option, to be able to deploy again :
- csi-vcd-controllerplugin
- csi-vcd-nodeplugin
Additional context
it seems that the csi templates aren't up to date either.
we have other problems after deleting v=5
(e.g. mkdir: cannot create directory 'test': Permission denied)