Comment 17 for bug 1971935

Could puppet classes be trying to handle the nfs services individually, and perhaps focusing on the var-lib-nfs-rpc_pipefs.mount unit, instead of letting the system start the dependencies as needed?

After I install nfs-common I seem to have the exact opposite of you: run-rpc_pipefs.mount is activated, and var-lib-nfs-rpc_pipefs.mount is not:

root@j-nfs:~# systemctl status var-lib-nfs-rpc_pipefs.mount
○ var-lib-nfs-rpc_pipefs.mount - RPC Pipe File System
     Loaded: loaded (/lib/systemd/system/var-lib-nfs-rpc_pipefs.mount; static)
     Active: inactive (dead)
      Where: /var/lib/nfs/rpc_pipefs
       What: sunrpc

root@j-nfs:~# systemctl status run-rpc_pipefs.mount
● run-rpc_pipefs.mount - RPC Pipe File System
     Loaded: loaded (/run/systemd/generator/run-rpc_pipefs.mount; generated)
     Active: active (mounted) since Fri 2022-07-01 12:35:05 UTC; 2min 17s ago
      Where: /run/rpc_pipefs
       What: sunrpc
      Tasks: 0 (limit: 1119)
     Memory: 20.0K
        CPU: 2ms
     CGroup: /system.slice/run-rpc_pipefs.mount

Jul 01 12:35:05 j-nfs systemd[1]: Mounting RPC Pipe File System...
Jul 01 12:35:05 j-nfs systemd[1]: Mounted RPC Pipe File System.