Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1113639
Description of problem: Please see the discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1101782 Ian came up with a patch Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. remove sssd caches (simulating a fresh system) 2. reboot 3. attempt to mount an autofs map w/o restarting either autofs or sssd Actual results: no maps were cached Expected results: autofs would retry, sssd would return the maps, shares would be mounted Additional info: SSSD autofs client should return a connection error in case no master map can be fetched from LDAP due to back end problems (as opposed to the map being simply absent from LDAP)
Fields changed
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => milestone: NEEDS_TRIAGE => SSSD 1.13 review: True => 0 selected: => testsupdated: => 0
Not needed for the next release
mark: => 0 milestone: SSSD 1.13 => SSSD 1.14 beta
milestone: SSSD 1.14 beta => SSSD 1.14.0 sensitive: => 0
cc: => muhammad.zali@t-systems.com
Unfortunately the autofs responder/provider work is still not started and we need to release the 1.14 version soon. Therefore, I'm bumping this ticket to the next version.
milestone: SSSD 1.14.0 => SSSD 1.16 beta
milestone: SSSD Future releases (no date set yet) => SSSD 1.15.2
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.15.2
Metadata Update from @jhrozek: - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Issue close_status updated to: None - Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.2)
Metadata Update from @jhrozek: - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue tagged with: cleanup-one-sixteen
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue untagged with: cleanup-one-sixteen - Issue tagged with: cleanup-future
Metadata Update from @jhrozek: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue untagged with: cleanup-future - Issue set to the milestone: SSSD Future releases (no date set yet) (was: SSSD 1.15.4)
Metadata Update from @pbrezina: - Issue assigned to pbrezina
Metadata Update from @thalman: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - Issue tagged with: bugzilla
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/3413
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.
Metadata Update from @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.