Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1353951
Description of problem: Regression of bz726475. This same test works fine with rhel7.2. Version-Release number of selected component (if applicable): sssd-1.14.0-0.2.beta1.el7 How reproducible: always Actual results: ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: : :: [ LOG ] :: performance_01: BZ726475 test for file descriptor leak ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: : :: [ BEGIN ] :: Running 'check_user_func' spawn ./check_user -n 1000 kau1 Password: User "kau1" authenticated successfully 1000 times :: [ PASS ] :: Command 'check_user_func' (Expected 0, got 0) :: [ PASS ] :: no sssd fd leaks: consistent 21 fds :: [ FAIL ] :: sssd_be fd leak: initial-22 final-23 :: [ PASS ] :: no sssd_pam fd leaks: consistent 21 fds :: [ FAIL ] :: sssd_nss fd leak: initial-23 final-24 '659e97fa-c85d-4900-8b12-3898d3a994e9' performance-01-BZ726475-test-for-file-descriptor-leak result: FAIL Expected results: Additional info:
This is not a full leak, but a bug nonetheless.
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => mark: no => 0 milestone: NEEDS_TRIAGE => SSSD 1.14.2 review: True => 0 selected: => testsupdated: => 0
Fields changed
owner: somebody => lslebodn status: new => assigned
summary: sssd_pam leaks file descriptors => Do not check local users with disabled local_negative_timeout
patch: 0 => 1
milestone: SSSD 1.14.2 => SSSD 1.14.1 resolution: => fixed status: assigned => closed
Metadata Update from @jhrozek: - Issue assigned to lslebodn - Issue set to the milestone: SSSD 1.14.1
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/4155
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.