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.

This bug was initially created as a copy of Bug #2136701

I am copying this bug because: to track fix for RHEL9



Description of problem:
Lower the severity of the log message for SSSD so that it is not shown at the default debug level.

Version-Release number of selected component (if applicable):
sssd-2.6.2-4.el8_6.1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Setup IPA-AD trust.
2. Enable 'auto_private_groups' option in sssd so that group with same name and gid=uid AD user is created automatically.
3. Check sssd_$domain.log:
---
(2022-06-08  8:52:40): [be[ipa.example.com]] [sysdb_add_user] (0x0040): [RID#3] Group named adadmin already exists in an MPG domain  <-----
(2022-06-08  8:52:40): [be[ipa.example.com]] [sysdb_add_user] (0x0400): [RID#3] Error: 17 (File exists)  <-----
---

Actual results:
Erroneous message is logged in /var/log/sssd/sssd_$domain.log file

Expected results:
Erroneous log message should not be shown at the default debug level.

Additional info:
Everything is working just fine like 'id' lookup & authentication. This is more like logging issue.

Upstream PR: https://github.com/SSSD/sssd/pull/6401

Pushed PR: https://github.com/SSSD/sssd/pull/6401

* `master`
    * 71466a8dbdb1d755ace15680cc2b4b11b68a0573 - SYSDB: pre-existence of MPG group in the cache isn't an error
* `sssd-2-8`
    * e0026e38c1a2c430e2eaebbdd09cf4332c722aca - SYSDB: pre-existence of MPG group in the cache isn't an error

Additional PR: https://github.com/SSSD/sssd/pull/6441

Pushed PR: https://github.com/SSSD/sssd/pull/6441

* `master`
    * e4dd11f2c2cd59031f904a1e30ed5b67edbdd54f - SYSDB: pre-existence of MPG group in the cache isn't an error
* `sssd-2-8`
    * cd1a94e58f64770d40bb995f35a8cab8c6f44ae9 - SYSDB: pre-existence of MPG group in the cache isn't an error

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 (sssd 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:2514