Bug 1219700 - F22 Beta: var-lib-nfs-rpc_pipefs.mount systemd unit fails on startup
Summary: F22 Beta: var-lib-nfs-rpc_pipefs.mount systemd unit fails on startup
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Atomic
Classification: Retired
Component: rpm-ostree
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Colin Walters
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1219871
TreeView+ depends on / blocked
 
Reported: 2015-05-08 01:32 UTC by Dusty Mabe
Modified: 2017-06-14 13:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1176758
: 1219871 (view as bug list)
Environment:
Last Closed: 2017-06-14 13:02:47 UTC
RHEL 7.3 requirements from Atomic Host:
Embargoed:

Attachments (Terms of Use)

Description Dusty Mabe 2015-05-08 01:32:03 UTC 
Description of problem:

Booting Atomic has a failed systemd unit. Details below:

-bash-4.3# 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 Thu 2015-05-07 15:50:56 UTC; 5h 45min ago
    Where: /var/lib/nfs/rpc_pipefs
     What: sunrpc
  Process: 460 ExecMount=/bin/mount sunrpc /var/lib/nfs/rpc_pipefs -n -t rpc_pipefs (code=exited, status=32)

May 07 15:50:56 localhost.localdomain mount[460]: mount: mount point /var/lib/nfs/rpc_pipefs does not exist
May 07 15:50:56 localhost.localdomain systemd[1]: var-lib-nfs-rpc_pipefs.mount mount process exited, code=exited status=32
May 07 15:50:56 localhost.localdomain systemd[1]: Failed to mount RPC Pipe File System.
May 07 15:50:56 localhost.localdomain systemd[1]: Unit var-lib-nfs-rpc_pipefs.mount entered failed state.


Version-Release number of selected component (if applicable):

Booted Fedora-Cloud-Atomic-22_Beta_TC8-20150405.x86_64.qcow2:
-bash-4.3# atomic host status
  TIMESTAMP (UTC)         VERSION   ID             OSNAME            REFSPEC                                                
* 2015-04-15 12:50:37     22.39     a8d8656489     fedora-atomic     fedora-atomic:fedora-atomic/f22/x86_64/docker-host
-bash-4.3# rpm -q rpm-ostree
rpm-ostree-2015.3-7.fc22.x86_64

How reproducible:

Always


Steps to Reproduce:
1. Run the F22 atomic image.
2. Look at systemctl output
Comment 1 Colin Walters 2015-05-08 12:57:41 UTC 
Ok so this is nfs-utils wanting a new empty directory in /var for a private mount point.

Possible fixes:

 - Move the directory to /run/nfs, have it be created by systemd-tmpfiles
 - Have nfs-utils create the directory
 - Change rpm-ostree to make empty directories
Comment 2 Dusty Mabe 2017-06-14 13:02:47 UTC 
I don't see this error in f25 atomic host:

```
[vagrant@vanilla-f25atomic ~]$ 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: active (mounted) since Wed 2017-06-14 12:32:26 UTC; 29min ago
    Where: /var/lib/nfs/rpc_pipefs
     What: sunrpc
  Process: 784 ExecMount=/usr/bin/mount sunrpc /var/lib/nfs/rpc_pipefs -t rpc_pipefs (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   Memory: 56.0K
      CPU: 5ms
   CGroup: /system.slice/var-lib-nfs-rpc_pipefs.mount

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
[vagrant@vanilla-f25atomic ~]$ 
[vagrant@vanilla-f25atomic ~]$ 
[vagrant@vanilla-f25atomic ~]$ rpm-ostree status
State: idle
Deployments:
● fedora-atomic:fedora-atomic/25/x86_64/docker-host
             Version: 25.137 (2017-06-04 23:31:40)
              Commit: 0ed61d7441eddf96e6a98de4f10f4675268c7888b6d2b8a405b8c21fe6c92d23
```
Note You need to log in before you can comment on or make changes to this bug.