Learn more about these different git repos.
Other Git URLs
On an IPA server I added a new automount location, baltimore, and created an indirect map and key /export/share.
On a client I configured sssd to use this automount location.
I was able to view files in /export/share.
Then I unconfigured automount in sssd (removed provider, autofs from services, etc). And restarted sssd.
Finally, I reconfigured sssd to use the default location.
I was still able to see the mount point from the baltimore location.
I made sure it was unmounted before reconfiguring automount.
As a test I stopped sssd, remove the cache and restarted sssd and autofs. I wasn't able to see the baltimore map after that.
sssd-1.8.92-0.20120605T1407Zgit7733e41.fc17
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.11 beta rhbz: => todo
proposed_priority: => Optional
This ticket has been evaluated for inclusion into SSSD 1.10 release and was decided to be excluded since it does not match the main goals and themes of the release. It might be considered for later releases.
milestone: SSSD 1.11 beta => SSSD 1.12 beta
We have a number of autofs-related tickets in the 1.14 bucket, but so far not many complaints about this bug, so I think it's a nice-to-have for 1.14
changelog: => design: => design_review: => 0 fedora_test_page: => mark: => 0 milestone: SSSD 1.14 beta => SSSD 1.14 backlog review: => 0 selected: => sensitive: => 0
Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.
milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)
Metadata Update from @rcritten: - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: Canditate to close
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/2411
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.