search

kubernetes-sigs / nfs-subdir-external-provisioner

Dynamic sub-dir volume provisioner on a remote NFS server.
Apache License 2.0
2.55k stars 755 forks source link

Does not create paths #225

Closed Gisleburt closed 1 year ago

Gisleburt commented 2 years ago

This could be a misconfiguration or misunderstanding on my part. I've gone with the manual setup.

When I add a new PersistentVolumeClaim, if the path that it will use does not already exist, then it fails to mount.

Pods fail to start, and using describe I get the following error:

Warning  FailedMount       22s (x8 over 88s)  kubelet            MountVolume.SetUp failed for volume "pvc-98196db3-4668-4ee5-b12e-55f416bb0a99" : mount failed: exit status 32
Mounting command: mount
Mounting arguments: -t nfs 10.0.147.154:/homelab/dns/pihole/pihole /var/lib/kubelet/pods/4d676af5-25c0-46bf-95f0-cfef48ed54af/volumes/kubernetes.io~nfs/pvc-98196db3-4668-4ee5-b12e-55f416bb0a99
Output: mount.nfs: mounting 10.0.147.154:/homelab/dns/pihole/pihole failed, reason given by server: No such file or directory
  Warning  FailedMount  22s (x8 over 88s)  kubelet  MountVolume.SetUp failed for volume "pvc-e9731c05-62b2-4301-93b9-3794d5bad620" : mount failed: exit status 32

If I go to my NFS server and manually create the path (eg, in this case /homelab/dns/pihole/pihole) then the pod creation works

My configuration can be seen here:

https://github.com/Gisleburt/homelab/blob/main/homelab/roles/storage-provider/templates/2.provisioner-storage-class.yaml

k8s-triage-robot commented 1 year ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 year 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 1 year ago

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

In response to [this](https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/issues/225#issuecomment-1366814270): >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.