Red Hat Bugzilla – Bug 1406164
Last modified: 2017-08-01 15:48:51 EDT
Description of problem:
systemd fails to mount /var/lib/nfs/rpc_pipefs because it runs before systemd-tmpfiles-setup.service, which creates the file structure there.
Version-Release number of selected component (if applicable):
# rpm-ostree status
Version: 7.3.1 (2016-11-30 02:14:24)
Steps to Reproduce:
1. Boot up 7.3.1-1.
/var/lib/nfs/rpc_pipefs isn't mounted.
/var/lib/nfs/rpc_pipefs is mounted.
As expected, doing `systemctl restart var-lib-nfs-rpc_pipefs.mount` later works.
This is also an issue in 7.3.0:
# rpm-ostree status
Version: 7.3 (2016-10-26 14:24:09)
# systemctl status var-lib-nfs-rpc_pipefs.mount
● var-lib-nfs-rpc_pipefs.mount - RPC Pipe File System
Loaded: loaded (/usr/lib/systemd/system/var-lib-nfs-rpc_pipefs.mount; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2016-12-19 21:16:26 UTC; 53s ago
Process: 581 ExecMount=/bin/mount sunrpc /var/lib/nfs/rpc_pipefs -t rpc_pipefs (code=exited, status=32)
Dec 19 21:16:26 localhost.localdomain mount: mount: mount point /var/lib/nfs/rpc_pipefs does not exist
This is tripping selinux issues in cloud-init and therefore blocking enablement progress on Azure at this point.
(In reply to Brent Baude from comment #2)
> This is tripping selinux issues in cloud-init and therefore blocking
> enablement progress on Azure at this point.
Well, it's *one* issue I noticed from your Azure logs. I'm still not sure if it's *the* issue blocking you currently. The machine should boot up fine without that mount succeeding (and it does over here).
It is tripping an OSError in cloud-init; hence the failure. Would be good to see this resolved so I can eliminate it as root cause and so forth
OK right, we need the same fix as upstream in https://bugzilla.redhat.com/show_bug.cgi?id=1219871 here:
Transferring to nfs-utils component.
Author: Colin Walters <email@example.com>
Date: Fri Jun 26 09:31:16 2015 -0400
systemd: Set var-lib-nfs-rpc_pipefs.mount After= tmpfiles
*** Bug 1427537 has been marked as a duplicate of this bug. ***
*** Bug 1293933 has been marked as a duplicate of this bug. ***
Thanks Jonathan for helping to verify this issue as comment #13.
No regression is found till now. Moving to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.