Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1320208
Description of problem: id user command does not list all groups after upgrade from sssd-1.12.4-47.el6.x86_64 to sssd-1.13.3-22.el6.x86_64 Version-Release number of selected component (if applicable): sssd-1.13.3-22.el6.x86_64 How reproducible: always Actual results: :: [ BEGIN ] :: bis_group_group_user2 :: actually running 'strict eval 'verify_output getent group bis_group_group_user2'' :: [ PASS ] :: bis_group_group_user2 (Expected 0, got 0) :: [ BEGIN ] :: bis_broken_user2 :: actually running 'strict eval 'verify_output id bis_broken_user2'' Unexpected output of id bis_broken_user2: uid=50002(bis_broken_user2) gid=60002(bis_broken_group_user2) groups=60002(bis_broken_group_user2) expecting: uid=50002(bis_broken_user2) gid=60002(bis_broken_group_user2) groups=60002(bis_broken_group_user2),60001(bis_broken_group_user1) :: [ FAIL ] :: bis_broken_user2 (Expected 0, got 1) :: [ BEGIN ] :: Running 'strict eval 'id localuser1 | grep localgroup1'' uid=1011(localuser1) gid=1011(localuser1) groups=1011(localuser1),1010(localgroup1) :: [ PASS ] :: Command 'strict eval 'id localuser1 | grep localgroup1'' (Expected 0, got 0) :: [ BEGIN ] :: Running 'strict eval 'su_success localuser1 Local_123'' :: [ PASS ] :: Command 'strict eval 'su_success localuser1 Local_123'' (Expected 0, got 0) Expected results: [root@vm-idm-003 ~]# id bis_broken_user2 uid=50002(bis_broken_user2) gid=60002(bis_broken_group_user2) groups=60002(bis_broken_group_user2),60001(bis_broken_group_user1) Additional info: purging the logs resolves the issue, but only a sssd restart does not resolve the issue [root@vm-idm-007 ~]# date Tue Mar 22 17:15:05 IST 2016 [root@vm-idm-007 ~]# id bis_broken_user2 uid=50002(bis_broken_user2) gid=60002(bis_broken_group_user2) groups=60002(bis_broken_group_user2) [root@vm-idm-007 ~]# service sssd restart Stopping sssd: [ OK ] Starting sssd: [ OK ] [root@vm-idm-007 ~]# id bis_broken_user2 uid=50002(bis_broken_user2) gid=60002(bis_broken_group_user2) groups=60002(bis_broken_group_user2) [root@vm-idm-007 ~]# date Tue Mar 22 17:15:32 IST 2016
Since this is not a regression and there is an easy workaround, I'm moving the ticket into 1.15
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => mark: no => 0 milestone: NEEDS_TRIAGE => SSSD 1.15 beta review: True => 0 selected: => testsupdated: => 0
Fields changed
owner: somebody => pcech
Metadata Update from @jhrozek: - Issue assigned to pcech - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman: - Custom field design_review adjusted to on (was: 0) - Custom field mark adjusted to on (was: 0) - Custom field patch adjusted to on (was: 0) - Custom field review adjusted to on (was: 0) - Custom field sensitive adjusted to on (was: 0) - Custom field testsupdated adjusted to on (was: 0) - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open) - Issue tagged with: Canditate to close
Bugzilla closes as NOTABUG
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/4020
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.