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.

Created attachment 1767705 [details]
Proposed fix (pure backport)

Description of problem:

Please backport Commit https://github.com/rsyslog/rsyslog/commit/c19ced96646fe6d7b18a35fa030ea3de7e6d25a8 to RHEL7's rsyslog.

When customers have "large" groups (150 users is enough, which isn't that large ...), rsyslog fails to execute actions having conditions on the group with following message:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
parameter 'XXX': ID for group testgrp could not be found
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

I tested that backporting the commit above is sufficient.


Version-Release number of selected component (if applicable):

rsyslog-8.24.0-57.el7_9.x86_64


How reproducible:

Always

Steps to Reproduce:
1. Create 150 users in a group

  # groupadd testgrp
  # for i in {1..150}; do adduser -G testgrp testuser${i}; done

2. Create an action conditioned by the group

  # echo '*.* action(type="omfile" FileCreateMode="0644" fileOwner="testuser1" fileGroup="testgrp" File="/tmp/logging")' > /etc/rsyslog.d/10.conf

3. Restart rsyslog


Actual results:

Error message above and log /tmp/logging not being updated

Expected results:

No failure

Additional info:

Patch in attachment.

*** Bug 1953897 has been marked as a duplicate of this bug. ***

Can we get this fixed for RHEL8 as well ? This is fixed in v8.2006 upstream but RHEL 8 comes with v9.1911.

RHEL8 fix is tracked by BZ#1944756

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 (rsyslog 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-2021:2312