-
Notifications
You must be signed in to change notification settings - Fork 260
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
StorageClass mountOptions not being applied to mount arguments #113
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
TiLogic
changed the title
StorageClass mountOptions not being applied mount arguments
StorageClass mountOptions not being applied to mount arguments
Dec 8, 2020
already fixed in master branch, e2e logs shows mountOptions are respected in CreateVolume:
While there is issue in DeleteVolume since it cannot get mountOptions by design. |
Many thanks! |
dobsonj
pushed a commit
to dobsonj/csi-driver-nfs
that referenced
this issue
Oct 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
NFS mountOptions not applied, causing NFS mount to fail.
Options:
{"mount_flags":["vers=3","nolock"]}}
Output:
Mounting arguments: -t nfs 10.0.0.58:/Users/user/dev/exports /tmp/pvc-85810e45-fc85-4dd7-8f63-a27b897104f9
What you expected to happen:
NFS mount options to be applied to the
mount
command.How to reproduce it:
The following StorageClass and PersistentVolumeClaims were used.
Anything else we need to know?:
Environment:
master
kubectl version
):v1.19.4
Fedora 32 (Server Edition)
uname -a
):Linux 5.9.11-100.fc32.x86_64
kubectl
remote installThe text was updated successfully, but these errors were encountered: