https://bugzilla.redhat.com/show_bug.cgi?id=876694 (Red Hat Enterprise Linux 6)
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Fix description: The code to check if the new superior entry exists or not was returning the "No such object" error only when the op was requested by the directory manager. This patch is removing the condition so that whoever the requester is, it returns the error.
git patch file (master) 0001-Trac-Ticket-520-RedHat-Directory-Server-crashes-segf.patch
Reviewed by Rich (Thank you!!)
Pushed to master: commit 40e68b1
Pushed to 389-ds-base-1.2.11: commit d4dbb3d
Just in case for those who are still using 1.2.10.x - here's the same patch backported to 1.2.10.25 (the backporting is trivial - only the line numbers change).
Patch backported to 1.2.10.25 0001-Trac-Ticket-520-1.2.10-RedHat-Directory-Server-crashes-segf.patch
To ssh://git.fedorahosted.org/git/389/ds.git cea00f8..51a1c48 389-ds-base-1.2.10 -> 389-ds-base-1.2.10 commit 51a1c48 Author: Noriko Hosoi nhosoi@totoro.usersys.redhat.com Date: Wed Nov 14 12:23:06 2012 -0800 (cherry picked from commit d4dbb3d)
Metadata Update from @pj101: - Issue assigned to nhosoi - Issue set to the milestone: 1.2.11.17
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/520
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: Fixed)
Login to comment on this ticket.