search

kubernetes-sigs / azurelustre-csi-driver

Apache License 2.0
12 stars 22 forks source link

"File name too long" when mounting Lustre PV in AKS #126

Closed pat-s closed 7 months ago

pat-s commented 1 year ago 
│   Normal   Scheduled    2m48s                default-scheduler  Successfully assigned workbench/workbench-78cf48884-m7x56 to aks-ds2v2-38810676-vmss000 │
│ 000                                                                                                                                                     │
│   Warning  FailedMount  45s                  kubelet            Unable to attach or mount volumes: unmounted volumes=[rstudio-home-storage], unattached │
│  volumes=[etc-rstudio rstudio-user license-file rstudio-home-storage rstudio-pam rstudio-session-secret kube-api-access-zk688 rstudio-prestart rstudio- │
│ ser-startup rstudio-session-config rstudio-secret rstudio-launcher-startup rstudio-config rstudio-rsw-startup session-templates[]: timed out waiting fo │
│ r the condition                                                                                                                                         │
│   Warning  FailedMount  37s (x8 over 2m45s)  kubelet            MountVolume.SetUp failed for volume "pvc-fef8f1e6-66c9-47d2-9a53-f1a57336bbc3" : rpc er │
│ ror: code = Internal desc = Could not mount "10.1.0.6@tcp:/lustreAKS" at "/var/lib/kubelet/pods/81e87d1b-ac73-458a-90f2-1a548f142dc5/volumes/kubernetes │
│ .io~csi/pvc-fef8f1e6-66c9-47d2-9a53-f1a57336bbc3/mount": mount failed: exit status 36                                                                   │
│ Mounting command: mount                                                                                                                                 │
│ Mounting arguments: --no-mtab--no-mtab -t lustre -o noatime,flock 10.1.0.6@tcp:/lustreAKS /var/lib/kubelet/pods/81e87d1b-ac73-458a-90f2-1a548f142dc5/vo │
│ lumes/kubernetes.io~csi/pvc-fef8f1e6-66c9-47d2-9a53-f1a57336bbc3/mount                                                                                  │
│ Output: mount.lustre: mount 10.1.0.6@tcp:/lustreAKS at /var/lib/kubelet/pods/81e87d1b-ac73-458a-90f2-1a548f142dc5/volumes/kubernetes.io~csi/pvc-fef8f1e │
│ 6-66c9-47d2-9a53-f1a57336bbc3/mount failed: File name too long

This also applies when shortening the PV name, i.e. the file name is still too long:

│ Output: mount.lustre: mount 10.1.0.6@tcp:/lustreAKS at /var/lib/kubelet/pods/e7028a7d-91d0-4070-9441-4e8f802cb134/volumes/kubernetes.io~csi/pv-wb-lustre/mount failed: file name too long │
│ e/mount failed: File name too long

What happened:

Error during PVC mount.

What you expected to happen:

Mount succeeds.

How to reproduce it:

Mount a dynamically created PVC using a Lustre SC as described in https://github.com/kubernetes-sigs/azurelustre-csi-driver/blob/main/docs/static-provisioning.md.

Anything else we need to know?:

Environment:

lianger commented 1 year ago

Lustre FS name has an 8 character max limit. If you are using AMLFS with AKS, the default fs-name is "lustrefs". This is static FS name for AMLFS.

joe-atzinger commented 1 year ago

This CSI is only currently supported for Azure Managed Lustre, using the guide here: https://learn.microsoft.com/en-us/azure/azure-managed-lustre/use-csi-driver-kubernetes

k8s-triage-robot commented 9 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 8 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 7 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 7 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/azurelustre-csi-driver/issues/126#issuecomment-2016427291): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.