Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionKaushik Banerjee
2013-09-19 13:15:36 UTC
Description of problem:
Group lookup is not returned immediately after sssd service startup
Version-Release number of selected component (if applicable):
sssd-1.11.0-1.el7
How reproducible:
Always
Steps to Reproduce:
1. Run the test with sleep of 1 second.
# service sssd stop; rm -f /var/lib/sss/{db,mc}/*;service sssd start;sleep 1;getent group kaugrp
Redirecting to /bin/systemctl stop sssd.service
Redirecting to /bin/systemctl start sssd.service
kaugrp:*:818410351:kautest
#
2. Run the test without any delay
# service sssd stop; rm -f /var/lib/sss/{db,mc}/*;service sssd start;getent group kaugrp
Redirecting to /bin/systemctl stop sssd.service
Redirecting to /bin/systemctl start sssd.service
#
Actual results:
Expected results:
Additional info:
(In reply to Pavel Březina from comment #6)
> Hi,
> the following scratch build contains a candidate patch. Can you test it
> please?
>
> https://brewweb.devel.redhat.com/taskinfo?taskID=6432935
With manual tests the fix looks good. Will test this build in our automation suite and give my feedback.
Verified in version 1.11.2-1.el7
# service sssd stop; rm -f /var/lib/sss/{db,mc}/*;service sssd start;getent group group1_dom1
Redirecting to /bin/systemctl stop sssd.service
Redirecting to /bin/systemctl start sssd.service
group1_dom1:*:770843749:user1_dom1
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: Group lookup is not returned immediately after sssd service startup Version-Release number of selected component (if applicable): sssd-1.11.0-1.el7 How reproducible: Always Steps to Reproduce: 1. Run the test with sleep of 1 second. # service sssd stop; rm -f /var/lib/sss/{db,mc}/*;service sssd start;sleep 1;getent group kaugrp Redirecting to /bin/systemctl stop sssd.service Redirecting to /bin/systemctl start sssd.service kaugrp:*:818410351:kautest # 2. Run the test without any delay # service sssd stop; rm -f /var/lib/sss/{db,mc}/*;service sssd start;getent group kaugrp Redirecting to /bin/systemctl stop sssd.service Redirecting to /bin/systemctl start sssd.service # Actual results: Expected results: Additional info: