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

nfsd cannot be started after upgrading to version 2023.4.0 #2560

Open
Andrea-Politi opened this Issue Mar 4, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@Andrea-Politi
Copy link

Andrea-Politi commented Mar 4, 2019

Issue Report

Bug

Container Linux Version

2023.4.0
NAME="Container Linux by CoreOS"
...
BUG_REPORT_URL="https://issues.coreos.com"

Environment

What hardware/cloud provider/hypervisor is being used to run Container Linux?
AWS

Expected Behavior

nfsd is started and all the persistent volume of this type are regularly mounted

Actual Behavior

all the pods containing a NFS volume remain in 'container creating' state

Reproduction Steps

  1. ... upgrade manually or automatically with update-engine
  2. ...

Other Information

apparently there are 2 systemd units failing on boot time: var-lib-nfs-rpc_pipefs.mount and proc-fs-nfsd.mount. the directories are created and exist, but even manually unmounting them does not fix the issue.

Mar 04 18:16:32 ip-192-168-36-78 systemd[1]: Mounting RPC Pipe File System...
-- Subject: Unit var-lib-nfs-rpc_pipefs.mount has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-lib-nfs-rpc_pipefs.mount has begun starting up.
Mar 04 18:16:32 ip-192-168-36-78 systemd[1]: Failed to set up mount unit: Invalid argument
Mar 04 18:16:32 ip-192-168-36-78 systemd[1]: Failed to set up mount unit: Invalid argument
Mar 04 18:16:32 ip-192-168-36-78 systemd[1]: Failed to set up mount unit: Invalid argument
Mar 04 18:16:32 ip-192-168-36-78 systemd[1]: Failed to set up mount unit: Invalid argument
Mar 04 18:16:32 ip-192-168-36-78 systemd[1]: Failed to set up mount unit: Invalid argument
Mar 04 18:16:32 ip-192-168-36-78 systemd[1]: var-lib-nfs-rpc_pipefs.mount: Mount process finished, but there is no mount.
Mar 04 18:16:32 ip-192-168-36-78 systemd[1]: var-lib-nfs-rpc_pipefs.mount: Failed with result 'protocol'.
Mar 04 18:16:32 ip-192-168-36-78 systemd[1]: Failed to mount RPC Pipe File System.
-- Subject: Unit var-lib-nfs-rpc_pipefs.mount has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-lib-nfs-rpc_pipefs.mount has failed.
@dm0-

This comment has been minimized.

Copy link
Member

dm0- commented Mar 8, 2019

What version did you upgrade from? I tried 1967.6.0, and the units worked before and after upgrade.

Did you edit the units? What is the output of systemctl cat proc-fs-nfsd.mount var-lib-nfs-rpc_pipefs.mount?

Do the direct mount commands work?

  • sudo mount -t nfsd nfsd /proc/fs/nfsd
  • sudo mount -t rpc_pipefs sunrpc /var/lib/nfs/rpc_pipefs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.