-
Notifications
You must be signed in to change notification settings - Fork 67
Open
Description
When installing knot-resolver 5.7.6 from EPEL9 on a system for the first time, the scriptlet that is supposed to set up the knot-resolver user and group fails to do so correctly, causing a host of installation problems.
Relevant logs from dnf install -y knot-resolver:
Running scriptlet: knot-resolver-5.7.6-1.el9.x86_64 30/31
Installing : knot-resolver-5.7.6-1.el9.x86_64 30/31
warning: user knot-resolver does not exist - using root
warning: group knot-resolver does not exist - using root
warning: user knot-resolver does not exist - using root
warning: group knot-resolver does not exist - using root
warning: user knot-resolver does not exist - using root
warning: group knot-resolver does not exist - using root
Running scriptlet: knot-resolver-5.7.6-1.el9.x86_64 30/31
/usr/lib/tmpfiles.d/knot-resolver.conf:4: Failed to resolve user 'knot-resolver': No such process
/usr/lib/tmpfiles.d/knot-resolver.conf:5: Failed to resolve user 'knot-resolver': No such process
/usr/lib/tmpfiles.d/knot-resolver.conf:6: Failed to resolve user 'knot-resolver': No such process
systemctl start [email protected] will then fail due to multiple file permission related errors.
To reproduce
The easiest way is to use a container. The same problem exists on full, physical hosts too.
# enter a fresh container
podman run --rm -it rockylinux:9 bash
# install knot-resolver; observe errors during installation
dnf install -y epel-release && dnf install -y [email protected]
# observe that the knot-resolver user and group have not been added correctly
grep knot-resolver /etc/{passwd,group}
# start knot-resolver and observe failures
systemctl start [email protected] && journalctl -u [email protected]A workaround
Currently it is possible to get a working installation with the following procedure:
- Install knot-resolver.
- Start the service with
systemctl start [email protected]and let it fail. Systemd will create theknot-resolveruser and group as declared in the service unit. - Uninstall knot-resolver.
- Install knot-resolver again. This time there won't be file permissions because the the
knot-resolveruser and group exist.
Metadata
Metadata
Assignees
Labels
No labels