Skip to content
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

Issue 2 with using the server-provisioner on top of mayastor backed storage class #149

Open
anmshkmr opened this issue Aug 31, 2024 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@anmshkmr
Copy link

anmshkmr commented Aug 31, 2024

Pod using the pvc made available by the nfs-server-provisioner start going through nfs mounting problems randomly

  Warning  FailedMount  31s (x3 over 37s)  kubelet  MountVolume.SetUp failed for volume "pvc-4f19b0cb-3a1a-4eb9-beb0-3eeeee8bc8d3" : mount failed: exit status 32
Mounting command: mount
Mounting arguments: -t nfs -o retrans=2,timeo=30,vers=3 10.43.107.108:/export/pvc-4f19b0cb-3a1a-4eb9-beb0-3eeeee8bc8d3 /var/lib/kubelet/pods/7e713802-ca23-486b-8355-005e2de07e0b/volumes/kubernetes.io~nfs/pvc-4f19b0cb-3a1a-4eb9-beb0-3eeeee8bc8d3
Output: mount.nfs: Operation not permitted for 10.43.107.108:/export/pvc-4f19b0cb-3a1a-4eb9-beb0-3eeeee8bc8d3 on /var/lib/kubelet/pods/7e713802-ca23-486b-8355-005e2de07e0b/volumes/kubernetes.io~nfs/pvc-4f19b0
  Warning  FailedMount  28s (x4 over 85s)  kubelet            MountVolume.SetUp failed for volume "pvc-4f19b0cb-3a1a-4eb9-beb0-3eeeee8bc8d3" : mount failed: exit status 32
Mounting command: mount
Mounting arguments: -t nfs -o retrans=2,timeo=30,vers=3 10.43.107.108:/export/pvc-4f19b0cb-3a1a-4eb9-beb0-3eeeee8bc8d3 /var/lib/kubelet/pods/c5abaf05-a953-43b4-96d8-6a04f1089b12/volumes/kubernetes.io~nfs/pvc-4f19b0cb-3a1a-4eb9-beb0-3eeeee8bc8d3
Output: mount.nfs: an incorrect mount option was specified for /var/lib/kubelet/pods/c5abaf05-a953-43b4-96d8-6a04f1089b12/volumes/kubernetes.io~nfs/pvc-4f19b0cb-3a1a-4eb9-beb0-3eeeee8bc8d3

Restarting the nfs-server-provisioner pod fixes it.

@k8s-triage-robot
Copy link

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

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants