#28 MOD operations with chained delete/add get back error 53 on backend config
Closed: wontfix None Opened 11 years ago by mkosek.


Description of problem:
We are trying to updated safely a few entries in cn=config,cn=ldbm
database,cn=plugins,cn=config in order to change limits.

We are using a modify operation with chained delete/add so that we change these
defaults only if admins haven't set their own.

DS is returning error 53 in this case (Unwilling to Perform).

It should just realize the operation is equivalent to a replace and let the
operation happen.

batch move to milestone 1.3

git merge ticket28
Updating 507b593..72b7e91
ldap/servers/slapd/configdse.c | 38 +++++++++++++++++++++++++++++++++++---
1 files changed, 35 insertions(+), 3 deletions(-)

[mareynol@localhost servers]$ git push
Counting objects: 11, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 1.19 KiB, done.
Total 6 (delta 4), reused 0 (delta 0)
To ssh://git.fedorahosted.org/git/389/ds.git
507b593..72b7e91 master -> master

Added initial screened field value.

move closed tickets to 1.3.0.a1

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.0.a1

6 years ago

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/28

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

2 years ago

Login to comment on this ticket.