Learn more about these different git repos.
Other Git URLs
When changing the auto_private_group setting from false to true, sss_cache -E or a restart does not reset the users primary GID.
% id uid=654401105(william) gid=654400513 groups=654400513,654401119(Workstation Operators) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 % sudo sss_cache -E % id uid=654401105(william) gid=654400513 groups=654400513,654401119(Workstation Operators) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
Current work around is:
systemctl stop sssd rm -rf /var/lib/sss/db/* systemctl start sssd
In general, this is not the first case where the sss_cache command is unable to control expiration of values correctly. I think that some time examining this command it's ability to correctly reset the cache is needed :)
Thank you!
What version are you running? I remember I saw this issue when I was working on the auto_private_groups feature, but I can't reproduce the problem with the current master. I guess the group renaming improvements that @fidencio was working on might have helped.
sssd-1.16.0-5.fc27.x86_64
Perhaps this will go away in f28 then :)
Give it a try updating on f27 :-) 1.16.1-4 is the latest available version.
Please reopen if you can reproduce the bug with the latest fedora update.
Metadata Update from @jhrozek: - Issue close_status updated to: worksforme - Issue status updated to: Closed (was: Open)
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4732
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.