Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1234756
Description of problem: cleanup task do not run in ipa-client Version-Release number of selected component (if applicable): sssd-1.12.4-42.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Set sssd.conf with following. subdomain_inherit = ldap_purge_cache_timeout ldap_purge_cache_timeout = 10 2. Do a user lookup getent passwd aduser1@sssdad.com 3. Extract the user to an LDIF file: ldbsearch -H /var/lib/sss/db/cache_sssdad.com.ldb objectclass=user > administrator.ldif 4. Edit the LDIF and set dataExpireTimestamp to "1" so that the entry is long expired 5. Add the user back and start sssd. This time the cleanup task will not run, so the user will stay in cache. 7. Clean up task executes only for main domain and not for subdomains. Actual results: Clean up task executes only for main domain and not for subdomains. Expected results: Clean up task executes and clear expired cache entries in main as well as subdomains. Additional info: I see the expected result only on IPA Server in trust to an AD. But from IPA Client, the expected results are not seen.
Fields changed
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => mark: no => 0 milestone: NEEDS_TRIAGE => SSSD Deferred review: True => 0 selected: => testsupdated: => 0
The corresponding downstream ticket was closed as well and since the cleanup task was disabled by default, it makes little sense to keep this ticket around.
resolution: => wontfix status: new => closed
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Patches welcome
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/3727
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.