Bug 1186023 - knot installed with transactional-update does not create knot group and user
Summary: knot installed with transactional-update does not create knot group and user
Status: RESOLVED DUPLICATE of bug 1185625
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: Other openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Michal Hrusecky
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-13 13:21 UTC by Enrico Belleri
Modified: 2022-04-30 00:40 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enrico Belleri 2021-05-13 13:21:18 UTC
Installing knot with transactional update is unable to create the group knot and user knot, also needed for create_dirs_from_rpmdb run by service create-dirs-from-rpmdb.service on boot.

Additional rpm output:
groupadd: Cannot determine your user name.
useradd: group 'knot' does not exist
warning: user knot does not exist - using root
warning: group knot does not exist - using root
/usr/lib/tmpfiles.d/knot.conf:3: Failed to resolve user 'knot': No such process
touch: cannot touch '/var/lib/systemd/sysv-convert/database': No such file or directory
/usr/lib/systemd/systemd-sysv-convert: line 25: /var/lib/systemd/sysv-convert/database: No such file or directory
/usr/lib/systemd/systemd-sysv-convert: line 40: /var/lib/systemd/sysv-convert/database: No such file or directory
Running in chroot, ignoring command 'daemon-reload'
Running in chroot, ignoring command 'try-restart'


This is solved by manually running:
$ groupadd -r knot
$ useradd -r -g knot -d /etc/knot -s /sbin/nologin -c "Knot DNS server" knot
Comment 1 Ignaz Forster 2021-06-21 15:36:53 UTC
I cannot reproduce this with a current MicroOS system.

Is this a system with SELinux enabled?
Comment 2 Enrico Belleri 2021-06-21 20:14:55 UTC
(In reply to Ignaz Forster from comment #1)
> I cannot reproduce this with a current MicroOS system.
> 
> Is this a system with SELinux enabled?

It happened with SELinux enforcing. I was using transactional-update 3.3.0
Comment 3 Ignaz Forster 2021-06-22 07:24:27 UTC
Ah, thanks for the info! This is a duplicate of bug 1185625 then, which was fixed in transactional-update 3.4.0.

*** This bug has been marked as a duplicate of bug 1185625 ***
Comment 4 OBSbugzilla Bot 2021-09-21 20:40:06 UTC
This is an autogenerated message for OBS integration:
This bug (1186023) was mentioned in
https://build.opensuse.org/request/show/920686 15.3 / knot
Comment 5 Swamp Workflow Management 2021-10-04 16:17:54 UTC
openSUSE-RU-2021:1331-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 1186023
CVE References: 
JIRA References: 
Sources used:
openSUSE Backports SLE-15-SP3 (src):    knot-3.1.2-bp153.2.3.2
Comment 6 OBSbugzilla Bot 2022-04-30 00:40:04 UTC
This is an autogenerated message for OBS integration:
This bug (1186023) was mentioned in
https://build.opensuse.org/request/show/973996 15.3 / knot