Are there any more details on how to reproduce this? I setup "chain on update" on a consumer, and I did a modify as the root DN on the consumer.
On 1.3.2(master), the update is rejected(err=53). On 1.3.1 is it allowed. Neither of these crash the server.
I followed this document for setting up chain on update: http://directory.fedoraproject.org/wiki/Howto:ChainOnUpdate
with the fix for #314 the updates as root are rejected by default, but it can be configured: nsslapd-distribution-root-update: local
I only experienced the crash once, created this ticket - but later on local updates as root did no longer crash. So there is a problem, but probably hard to reproduce
Replying to [comment:5 lkrispen]:
with the fix for #314 the updates as root are rejected by default, but it can be configured: nsslapd-distribution-root-update: local I only experienced the crash once, created this ticket - but later on local updates as root did no longer crash. So there is a problem, but probably hard to reproduce
Did it crash before your patch or after? Should I be testing 1.3.1, or master with the config change you mentioned?
The crash occured when I started to implement #314, so it was before, but with a state of master late august/early sept. So I suggest you try with current master and the switch to allow local updates
I have been unable to reproduce this crash. I've tried all kinds of scenarios, consumers, hubs, single masters, changelog/no changelog, etc. I wonder if while implementing ticket #314, the crash was accidentally introduced, and then later accidentally fixed.
Closing ticket.
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.3 - 10/13 (October)
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/840
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.