You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to upgrade vsphere csi driver in rancher rk1 from 2.5.1 to 2.7.0 (and also tried to 3.0.1), controller is not starting, having following error:
flag provided but not defined: -use-gocsi
Fri, Jun 16 2023 3:35:04 pmUsage of /bin/vsphere-csi:
Fri, Jun 16 2023 3:35:04 pm -fss-name string
Fri, Jun 16 2023 3:35:04 pm Name of the feature state switch configmap
Fri, Jun 16 2023 3:35:04 pm -fss-namespace string
Fri, Jun 16 2023 3:35:04 pm Namespace of the feature state switch configmap
Fri, Jun 16 2023 3:35:04 pm -kubeconfig string
Fri, Jun 16 2023 3:35:04 pm Paths to a kubeconfig. Only required if out-of-cluster.
Fri, Jun 16 2023 3:35:04 pm -supervisor-fss-name string
Fri, Jun 16 2023 3:35:04 pm Name of the feature state switch configmap in supervisor cluster
Fri, Jun 16 2023 3:35:04 pm -supervisor-fss-namespace string
Fri, Jun 16 2023 3:35:04 pm Namespace of the feature state switch configmap in supervisor cluster
Fri, Jun 16 2023 3:35:04 pm -version
Fri, Jun 16 2023 3:35:04 pm Print driver version and exit
What you expected to happen:
Controller to start
How to reproduce it (as minimally and precisely as possible):
@cristi-vlad What manifests are you using to upgrade to 2.7.0 or 3.0.1?
We used to have a use-gocsi flag in our deployment yamls until 2.5 release. But we completely removed gocsi usage from 2.6 release with this MR.
You need to use the deployment yamls from 2.7.x or 3.0.x releases for the upgrade.
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
When trying to upgrade vsphere csi driver in rancher rk1 from 2.5.1 to 2.7.0 (and also tried to 3.0.1), controller is not starting, having following error:
What you expected to happen:
Controller to start
How to reproduce it (as minimally and precisely as possible):
Upgrade or fresh install to 2.7.0 or 3.0.1
Anything else we need to know?:
Environment:
csi-vsphere version: 2.7.0 / 3.0.1
vsphere-cloud-controller-manager version:
tested versions for 3.0.1:
csiController:
driver: v3.0.1
attacher: v4.2.0
resizer: v1.7.0
livenessprobe: v2.9.0
syncer: v3.0.1
provisioner: v3.4.0
csiNode:
driver: v3.0.1
registrar: v2.7.0
livenessprobe: v2.9.0
tested versions for 2.7.0:
csiController:
driver: v2.7.0
attacher: v3.5.0
resizer: v1.5.0
livenessprobe: v2.7.0
syncer: v2.7.0
provisioner: v3.2.1
csiNode:
driver: v2.7.0
registrar: v2.5.1
livenessprobe: 2.7.0
Kubernetes version: 1.23.16
Rancher version: 2.7.5
vSphere version: n/a
OS (e.g. from /etc/os-release): Rancher/rk1/linux
Kernel (e.g.
uname -a
): n/aInstall tools: terraform
Others: n/a
The text was updated successfully, but these errors were encountered: