#6931 custodia user isn't created when FreeIPA RPMs are installed
Closed: fixed Opened by tkrizek.

Problem

After freeipa rpms are installed and system is rebooted, journald reports errors about non-existent user custodia.

When reproduced in a Fedora 25 vagrant box, it causes the improper system startup causes authentication failures for non-root users:

Authentication failed.
"System is booting up. See pam_nologin(8)"
May 05 11:39:14 master.ipa.test sshd[13642]: fatal: Access denied for user vagrant by PAM account configuration [preauth]

Steps to reproduce

  1. Install FreeIPA RPMs
  2. systemctl reboot

Logs

  • journalctl
May 05 13:22:40 localhost systemd[1]: Failed to start Create Volatile Files and Directories.
May 05 13:22:40 localhost systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
May 05 13:22:40 localhost systemd-tmpfiles[928]: Cannot set file attribute for '/var/log/journal/0997fc149f9f4ac8a69a83a3546999c1', value=0x00800000, mask=0x00800000: Operation not supporte
May 05 13:22:40 localhost systemd-tmpfiles[928]: Cannot set file attribute for '/var/log/journal', value=0x00800000, mask=0x00800000: Operation not supported
May 05 13:22:39 localhost systemd-tmpfiles[928]: [/usr/lib/tmpfiles.d/custodia.conf:1] Unknown user 'custodia'.

Metadata Update from @pvoborni:
- Issue set to the milestone: FreeIPA 4.7
- Issue tagged with: tracker

What are the user properties (homedir, shell, comment, etc.) to create the user manually for the time being?

I've just grabbed them from the spec: https://src.fedoraproject.org/rpms/custodia/blob/master/f/custodia.spec

The issue has been fixed in the custodia package. User and group are now created on package installation time. I haven't seen the warning in a while, too.

Metadata Update from @cheimes:
- Issue close_status updated to: fixed

Metadata