Bug 1921315
| Summary: | Unexpected interaction between overriding the primary group and the 'auto_private_groups = true' option | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Rakesh Kumar <rakkumar> |
| Component: | sssd | Assignee: | Sumit Bose <sbose> |
| Status: | CLOSED MIGRATED | QA Contact: | sssd-qe |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.4 | CC: | aboscatt, atikhono, chaithco, grajaiya, jwooten, lslebodn, mzidek, pbrezina, rgarcia, sbose, tscherf |
| Target Milestone: | beta | Keywords: | MigratedToJIRA, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-18 23:52:57 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
Rakesh Kumar
2021-01-27 21:19:32 UTC
Hi,
A shorter reproducer is to call
getent group 974001183
getent group 974001212
after changing the primary group to 974001212 and restarting SSSD on the
your test system. I get:
[root@ipaserver ~]# getent -s sss group 974001183
testuser80:*:974001212:
[root@ipaserver ~]# getent -s sss group 974001212
testuser80:*:974001212:
The first lookup is with the original primary GID of the user but due
to the override it is returned with the overridden primary GID which is
wrong. Unfortunately the memory cache save the GID with the wrong group
name for some time before it can be refreshed and as a result the lookup
with the new GID also returns the wrong name.
bye,
Sumit
Upon inspection CNV is not dependent upon this bug. Please add us again if you deem so. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |