search

hpe-storage / csi-driver

A Container Storage Interface (CSI) driver from HPE
https://scod.hpedev.io
Apache License 2.0
62 stars 57 forks source link

MountVolume.MountDevice failed for volume #343

Open husseinallaw opened 1 year ago

husseinallaw commented 1 year ago

i followed the steps from this link :

https://scod.hpedev.io/learn/persistent_storage/index.html#installing_the_helm_chart

all was fine and the PVC got created in our namespace and it is bound, and i can also see the PVC created on Nimble Storage however whenever i install any pod like nginx, it get's stuck and i get the below error when launching the pod :

.Successfully assigned hpe-storage/nginx to alssworker1.areeba.com .AttachVolume.Attach succeeded for volume "pvc-5118ca53-c33c-499a-a439-e480bc4815aa" .unable to attach or mount volumes: unmounted volumes=[config], unattached volumes=[config kube-api-access-85dnm]: timed out waiting for the condition

MountVolume.MountDevice failed for volume "pvc-5118ca53-c33c-499a-a439-e480bc4815aa" : rpc error: code = Internal desc = Failed to stage volume 0656c0fe884312fd06000000000000000000000025, err: rpc error: code = Internal desc = Error creating device for volume 0656c0fe884312fd06000000000000000000000025, err: device not found with serial 6c8379f43c4dcc6a6c9ce9008e03d215 or target

datamattsson commented 1 year ago

I apologize no one got to this, are you still having issues @husseinallaw?

pavankumar-go commented 1 year ago

I'm seeing this issue.

Warning FailedMount 9s (x3 over 73s) kubelet MountVolume.MountDevice failed for volume "pvc-ae12f06b-4933-43ed-8e44-607587b98973" : rpc error: code = Internal desc = Failed to stage volume 06766d9dd0b83f1e9100000000000000000000001e, err: rpc error: code = Internal desc = Error creating device for volume 06766d9dd0b83f1e9100000000000000000000001e, err: device not found with serial 8db26d8748dc42016c9ce900418352ce or target

datamattsson commented 1 year ago

The error indicates that the device can't be discovered on the host. In most cases there's a data and multipath setup issue. Does the worker nodes have access to the data interfaces on the array?