Open hughdanliu opened 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
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/kind bug
What happened? I attempted to mount an FSx for OpenZFS file system on an application pod using NFSv3 and received this error:
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
kubectl version
): 1.24