Unable to attach or mount volumes

ofek / csi-gcs

Kubernetes CSI driver for Google Cloud Storage

https://ofek.dev/csi-gcs/

Apache License 2.0

152 stars 39 forks source link

Unable to attach or mount volumes #71

Open jailbreakerSN opened 3 years ago

jailbreakerSN commented 3 years ago

Hello,

I'm facing a issu when trying to test csi-gcs on GKE after creating the secret csi-gcs-secret

kubectl create secret generic csi-gcs-secret --from-literal=bucket= --from-file=key=
kubectl apply -k "github.com/ofek/csi-gcs/examples/static?ref=v0.7.0" The errors I got are:
AttachVolume.Attach failed for volume "csi-gcs-pv" : attachdetachment timeout for volume csi-gcs
Unable to attach or mount volumes: unmounted volumes=[csi-gcs-pvc], unattached volumes=[csi-gcs-pvc default-token-n6w8k]: timed out waiting for the condition

jailbreakerSN commented 3 years ago

@ofek can you check please my issue? Thanks in advance!

ofek commented 3 years ago

@dysosmus Do you think this might be related to https://github.com/ofek/csi-gcs/pull/72?

dysosmus commented 3 years ago

@ofek I can observe similar events in our clusters and it's related to the driver starting up. In our case, those warnings are however transitory and doesn't prevent the pod from eventually start.

jailbreakerSN commented 3 years ago

Or course @dysosmus, it doesn't prevent the pod from start, but stay at containairizing step, because it seems to wait for a volume that never provided !

dysosmus commented 3 years ago

it doesn't prevent the pod from start, but stay at containairizing step, because it seems to wait for a volume that never provided !

@ofek Then that seem different, from what I'm working on #72 :( . In my experience, the container eventually start after ±1-2 minutes of retries.

@jailbreakerSN is the csi-gcs driver pod is running properly on the node where your pod is running?

jailbreakerSN commented 3 years ago

Hello @dysosmus , Yes, I think all is running (same namespace, same node) like the commands I specified earlier. I put the Key and bucket Bâle correctly and ran out with kubectl

ofek commented 3 years ago

@maennchen Do you have any ideas?

jailbreakerSN commented 3 years ago

@ofek @dysosmus , might it be related to the status of my cluster, which is a private cluster?

dysosmus commented 3 years ago

@jailbreakerSN could be, do your subnet where your GKE cluster nodes are running have Google Private Access enabled? You can also try to spin up a GCP Cloud NAT on the subnet, but afaik that shouldn't be needed if Private Access is enabled.

maennchen commented 3 years ago

@jailbreakerSN Can you capture the log of the csi-gcs DaemonSet pods while you provision a new PVC and start a pod using it?

elamcheliyan commented 2 years ago

@jailbreakerSN , Is this issue still present? even I want to try this in my GKE services