Bug 2136791

Summary: Lower the severity of the log message for SSSD so that it is not shown at the default debug level.
Product: Red Hat Enterprise Linux 9 Reporter: Alexey Tikhonov <atikhono>
Component: sssdAssignee: Alexey Tikhonov <atikhono>
Status: CLOSED ERRATA QA Contact: shridhar <sgadekar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.1CC: pasik, pbrezina, sgadekar
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sync-to-jira
Fixed In Version: sssd-2.8.2-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 08:19:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alexey Tikhonov 2022-10-21 10:44:27 UTC
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.

Comment 1 Alexey Tikhonov 2022-10-21 11:09:55 UTC
Upstream PR: https://github.com/SSSD/sssd/pull/6401

Comment 2 Alexey Tikhonov 2022-11-01 16:35:28 UTC
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

Comment 5 Alexey Tikhonov 2022-11-16 20:29:49 UTC
Additional PR: https://github.com/SSSD/sssd/pull/6441

Comment 6 Alexey Tikhonov 2022-12-02 15:23:02 UTC
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

Comment 13 errata-xmlrpc 2023-05-09 08:19:51 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 (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