[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-13 Thread Andreas Hasenack
** Changed in: nfs-utils (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title: Invalid pipefs-

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-13 Thread Stefan Staeglich
** Changed in: nfs-utils (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title: Invalid pipefs-directory prevents rpc-gssd.service from starting

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-13 Thread Anders Larsson
Sorry for the late response. From what I can see we don't really implement any dependency chain when configuring NFS/Kerberos on Ubuntu. We haven't seen this issue in earlier releases of Ubuntu (20.04 and earlier) though. But seems like the process worked differently at that point since /etc/nfs.co

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-13 Thread Stefan Staeglich
Adjusting the nfs.conf mitigates the issue as there is a mount unit var-lib-nfs-rpc_pipefs.mount: [general] pipefs-directory=/var/lib/nfs/rpc_pipefs/ So the package postinst script should just call the generator or the default of pipefs-directory should match the default mount unit -- You recei

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-13 Thread Stefan Staeglich
We are also affected by this issue. I would like to avoid to schedule a reboot in my automation script as this can run multiple times as this maintains the whole sssd config. So I would like to avoid unexpected reboots. -- You received this bug notification because you are a member of Ubuntu Bugs

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-06 Thread Anders Larsson
I can add more information on Monday when I'm working again. I suspect we found this issue because it was manually developed/tested to ensure that everything works. That is without going through the normal provisioning chain. As part of our provisioning chain one step is usually to restart the sys

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-06 Thread Andreas Hasenack
> We're using Puppet to configure our systems and one of the steps is to ensure > gss-rpcd.service is > up and running. Can you come up with the ordering in which this nfs host is provisioned, in terms of nfs and kerberos configuration and such? I concur that having to reboot is not ideal. --

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-06 Thread Anders Larsson
We're using Puppet to configure our systems and one of the steps is to ensure gss-rpcd.service is up and running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title: Invalid pipefs-director

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-06 Thread Anders Larsson
Hello, You're correct. The use-case is to mount Kerberos secured NFS mount points. All other configuration is working as expected since after a reboot (as mentioned earlier) the system in question is able to successfully mount with krb5. Thanks. -- You received this bug notification because you

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-06 Thread Andreas Hasenack
The commit that introduced the generator has this explanation: commit 3892174834ea1a4729348f0ecd3078cc1d5458e4 Author: Scott Mayhew Date: Mon Apr 10 07:10:45 2017 -0400 systemd: add a generator for the rpc_pipefs mountpoint The nfs.conf has config options for the rpc_pipefs mountpo

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-06 Thread Andreas Hasenack
But I would still like to understand how you arrived at gssd complaining about the pipefs mount. Were you just trying to start it manually? ** Changed in: nfs-utils (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, whic

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-06 Thread Andreas Hasenack
Can you elaborate a bit on your scenario? Since you are trying to start gssd, I assume you have a kerberos environment, and the server has a keytab in /etc/krb5.keytab (which is a condition for the gssd service to start). In my tests, I also usually reboot the server after installing all the nfs a

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nfs-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title:

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-06 Thread Anders Larsson
After restarting the system /run/rpc_pipefs exists because /run/systemd/generator/run-rpc_pipefs.mount is created and rpc-gssd works correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Ti

[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting

2022-05-06 Thread Anders Larsson
** Description changed: Ubuntu 22.04 Server + Package version: 1:2.6.1-1ubuntu1 Package nfs-common/nfs-utils provides /etc/nfs.conf and /lib/systemd/system/rpc-gssd.service. /etc/nfs.conf (and seems to be copied from /usr/share/nfs-common/conffiles/nfs.conf) has the configuration: ...