#49329 Provide descriptive error message when neither suffix nor backend is specified for USN cleanup task
Closed: wontfix Opened by ilias95.

Issue Description

Providing either a suffix or backend attribute is necessary in order to create a USN tombstone cleanup entry. Otherwise the server will not accept the operation. However in this case it just returns a general error message which is not helpful at all: "ldap_add: Bad parameter to an ldap routine (-9)". We should replace this with a descriptive error message.

Steps to reproduce

Apply the following LDIF:

dn: cn=Example,cn=USN tombstone cleanup task,cn=tasks,cn=config
changetype: add
objectClass: top
objectClass: extensibleObject

Metadata Update from @ilias95:
- Issue assigned to ilias95

Metadata Update from @ilias95:
- Custom field type adjusted to defect

Metadata Update from @ilias95:
- Custom field reviewstatus adjusted to review

commit dfc8896036516c070f6c298a622f944e59c1465c
To ssh://git@pagure.io/389-ds-base.git
dda766a..dfc8896 master -> master

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to ack (was: review)

Metadata Update from @ilias95:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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

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)

Metadata