-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AttachVolume.Attach failed for volume "pvc-3d1d6dfb-39c3-11e9-9185-fa163e02d826" : node has no NodeID annotation #126
Comments
Hi Darcy, what version of Kubernetes are you running on? |
Hi David,
|
@darcyllingyan This looks like a known issue that we fixed in Kubernetes 1.13. We will look into cherry-picking the change into 1.12 which would put it in the next patch release. For now the workaround would be to remove your driver from the cluster and then deploy it again. That should solve the issue in most cases |
Hi David,
You mean I remove the the sidecar containers(external-attacher, external-provosioner, node-driver-registratar) and the driver, then deploy again? This method seems don't take effect as I have remove/deploy several times. Thanks |
Hi David,
|
@darcyllingyan what was the sequence of steps you followed? I believe in
Let me know if that is not the case, there may be another bug we need to look into... |
@darcyllingyan to clarify, in your top post you did not have the CRD installed and did not enable CSINodeInfo feature gate, right? |
@davidz627 ,@verult,
Note: In the guide, minimum requirement of node-driver-registrar is v1.13 https://github.com/kubernetes-csi/node-driver-registrar#compatibility , I'm not sure whether this workaround can take effect for the node-driver-registrar? Thanks |
The CSINodeInfo feature gate needs to be set to true on both apiserver and kubelet as well |
If there's a gap in our documentation about enabling this feature gate please let us know, thanks! |
@verult ,
In fact, I have enabled the CSINodeInfo(not only CSIDriverRegistry) feature-gates both on apiserver and kubelet, but it still shows nothing for the
Thanks |
Would you mind sharing your DaemonSet spec for the node deployment? I'm wondering if node-driver-registrar args are set correctly. The other thing I could think of is GetNodeId isn't implemented correctly, but if you are using a published Cinder driver it's probably OK. |
As I don't have a Kubernetes 1.12 and only Kubernetes 1.13, will close the issue now and will try later when I have Kubernetes 1.12. |
Hi,
I have created the CSI plugin in my kubernetes cluster, now the SC, pvc, pv has been created successfully. But when create pod to attach the volume, it always reports the error "AttachVolume.Attach failed for volume "pvc-3d1d6dfb-39c3-11e9-9185-fa163e02d826" : node "sdc-bcmt-01-edge-worker-01" has no NodeID annotation"
Below is the detailed log for attacher container:
attacher00.log
Thanks
The text was updated successfully, but these errors were encountered: