Learn more about these different git repos.
Other Git URLs
Currently, it's difficult to debug the krb5_child and ldap_child processes, as they are forked from the sssd_be process.
It would be a good idea for long-term maintenance if we wrote a simulator that could invoke these children directly and pass sample input to the child.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.9.0 NEEDS_TRIAGE
milestone: SSSD 1.9.0 NEEDS_TRIAGE => SSSD Kerberos improvements
rhbz: => 0
feature_milestone: => owner: somebody => jhrozek patch: 0 => 1 status: new => assigned
proposed_priority: => Nice to have
Note that I implemented a test program for the krb5_child when I was developing the dircache feature.
It needs extending and there is no ldap_child test program.
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: SSSD Kerberos Improvements Feature => SSSD 1.10 beta
priority: major => minor
selected: => Not need
Moving tickets that are not a priority for SSSD 1.10 into the next release.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
changelog: => design: => design_review: => 0 fedora_test_page: => milestone: SSSD 1.13 beta => Interim Bucket priority: minor => major review: => 0
milestone: Interim Bucket => SSSD 1.12 beta
The scope is to implement an ldap_child test program, krb5_child test already exists. Since we don't plan any changes to the ldap_child, I think we can push this one out.
review: 0 => 1
milestone: SSSD 1.12 beta => SSSD 1.14 beta
We ended up implementing full integration tests which serve a very similar purpose, albeit less programmable maybe.
mark: => 0 milestone: SSSD 1.14 beta => SSSD 1.15 beta sensitive: => 0
Since we have integration tests, I think it's fine to defer this one.
selected: Not need => May
Most of the functionality would be covered by integration tests. Some corner cases might still be nice to be tested with unit tests, but I think this ticket can safely be deferred.
milestone: SSSD Future releases (no date set yet) => SSSD Patches welcome
Metadata Update from @sgallagh: - Issue assigned to jhrozek - Issue set to the milestone: SSSD Patches welcome
Metadata Update from @jhrozek: - Assignee reset
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - 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/2169
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.