https://bugzilla.redhat.com/show_bug.cgi?id=743703
Description of problem: We have several documented cases where customers have installed DS on a server that also serves as an NFS mountpoint (usually home directories). This configuration is known to cause problems with DS. Removing the NFS mountpoint resolves. We need to document this as a "do not do this" Version-Release number of selected component (if applicable): all How reproducible: every time Steps to Reproduce: 1.setup nfs mountpoints via /etc/export 2.install and configure ds to serve those clients that will use nfs 3. Actual results: ds will stop servicing the requests Expected results: this is expected. We need to document that ds cannot be on an NFS server. Additional info: We see a surprising number of ds installs configured this way.
Added initial screened field value.
Metadata Update from @nkinder: - Issue assigned to rmeggins - Issue set to the milestone: N/A
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/235
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 @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.