RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2095422 - [RFE] haproxy use systemd-sysusers
Summary: [RFE] haproxy use systemd-sysusers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: haproxy
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.2
Assignee: Ryan O'Hara
QA Contact: Juraj Hrdlica
URL:
Whiteboard:
Depends On:
Blocks: 2134206
TreeView+ depends on / blocked
 
Reported: 2022-06-09 17:20 UTC by Pat Riehecky
Modified: 2023-05-09 09:02 UTC (History)
4 users (show)

Fixed In Version: haproxy-2.4.17-4.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2134206 (view as bug list)
Environment:
Last Closed: 2023-05-09 07:46:47 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-6314 0 None None None 2022-12-26 04:07:47 UTC
Red Hat Issue Tracker RHELPLAN-124852 0 None None None 2022-06-09 17:21:39 UTC
Red Hat Product Errata RHBA-2023:2336 0 None None None 2023-05-09 07:47:00 UTC

Description Pat Riehecky 2022-06-09 17:20:32 UTC
Description of problem:
haproxy is using static useradd scripts

Version-Release number of selected component (if applicable):
haproxy-2.4.17-2.el9

How reproducible:
100%

Steps to Reproduce:
1.review %pre
2.
3.

Actual results:
%pre
getent group %{haproxy_group} >/dev/null || \
    groupadd -r %{haproxy_group}
getent passwd %{haproxy_user} >/dev/null || \
    useradd -r -g %{haproxy_user} -d %{haproxy_homedir} \
    -s /sbin/nologin -c "haproxy" %{haproxy_user}
exit 0

Expected results:
use of system-sysusers 

Additional info:
https://www.freedesktop.org/software/systemd/man/systemd-sysusers.html
https://fedoraproject.org/wiki/Changes/Adopting_sysusers.d_format

Comment 2 Ryan O'Hara 2022-10-12 20:54:36 UTC
I don't see any risk in changing this in RHEL9.2 so setting dev ack. This change has been pushed to rawhide and F37 and I didn't notice any issues.

Comment 11 Juraj Hrdlica 2023-02-27 14:04:20 UTC
Tested in haproxy-2.4.17-4.el9

haproxy.spec contains:
%pre
%sysusers_create_compat %{SOURCE5}

Comment 15 errata-xmlrpc 2023-05-09 07:46:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (haproxy bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2336


Note You need to log in before you can comment on or make changes to this bug.