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
Helm Deployment of Nutanix-csi-storage 3.1.0 on vanilla kubernetes
To reproduce error:
nutanix-csi-storage
/values.yaml
Set
kubernetesClusterDeploymentType: "bare-metal"
My PC is on 2024.2.
Creation of SC, PV, PVC are all successfully.
But on mount,
AttachVolume.Attach failed for volume rpc error: code = NotFound desc = bad CSI nodeId format: #ip of node#
Nutanix support ticket 01844179.
The SRE does not seem to have knowledge about kubelet registration of CSI driver.
I hope that the dev can take a look at what causes the CSI driver to register nodeid with invalid char #.
If I set kubernetesClusterDeploymentType: "non-bare-metal", the new csi went to take the machine-id and attempt to use that as the vm uuid when querying the PC API.
The text was updated successfully, but these errors were encountered:
Helm Deployment of Nutanix-csi-storage 3.1.0 on vanilla kubernetes
To reproduce error:
nutanix-csi-storage
/values.yaml
Set
kubernetesClusterDeploymentType: "bare-metal"
My PC is on 2024.2.
Creation of SC, PV, PVC are all successfully.
But on mount,
AttachVolume.Attach failed for volume rpc error: code = NotFound desc = bad CSI nodeId format: #ip of node#
Nutanix support ticket 01844179.
The SRE does not seem to have knowledge about kubelet registration of CSI driver.
I hope that the dev can take a look at what causes the CSI driver to register nodeid with invalid char #.
If I set kubernetesClusterDeploymentType: "non-bare-metal", the new csi went to take the machine-id and attempt to use that as the vm uuid when querying the PC API.
The text was updated successfully, but these errors were encountered: