search

kubernetes-sigs / aws-fsx-openzfs-csi-driver

Amazon FSx for OpenZFS Cloud Container Storage Interface(CSI) Driver
Apache License 2.0
22 stars 8 forks source link

NFSv3 Mounts fail unless the --nolock mount option is specified #61

Open hughdanliu opened 4 months ago

hughdanliu commented 4 months ago

/kind bug

What happened? I attempted to mount an FSx for OpenZFS file system on an application pod using NFSv3 and received this error:

Output: mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: mounting ___ failed, reason given by server: No such file or directory

Even though the rpc-statd service was running on the node. What you expected to happen? NFSv3 mounts succeed without needing to provide the nolock mount option.

How to reproduce it (as minimally and precisely as possible)? Attempt to mount a file system using NFSv3

Anything else we need to know?: Nope

Environment

hughdanliu commented 4 months ago

This is likely an issue with the node daemonset pod permissions. This could possibly be fixed by making the communication policies between the node pods and the host more lenient, allowing for the node daemonset pods to interact with the rpcbind and rpc-statd services running on the node.

I tried setting

on the node daemonset pods This got me around the rpc.statd missing error, but produced this error:

mount.nfs: access denied by server while mounting
k8s-triage-robot commented 1 month 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

hughdanliu commented 3 weeks ago

/remove-lifecycle stale