Provide descriptive error message when neither suffix nor backend is specified for USN cleanup task

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49329

• Created at 2017-07-20 22:24:18 by ilias95 (@ilstam)
• Closed at 2017-07-28 15:20:06 as fixed
• Assigned to ilias95 (@ilstam)

---

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

[389-ds-bot]

Comment from ilias95 (@ilstam) at 2017-07-20 22:24:25

Metadata Update from @ilstam:

• Issue assigned to ilstam

[389-ds-bot]

Comment from ilias95 (@ilstam) at 2017-07-21 02:40:57

[389-ds-bot]

Comment from ilias95 (@ilstam) at 2017-07-21 02:40:59

Metadata Update from @ilstam:

• Custom field type adjusted to defect

[389-ds-bot]

Comment from ilias95 (@ilstam) at 2017-07-21 02:41:17

Metadata Update from @ilstam:

• Custom field reviewstatus adjusted to review

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2017-07-24 01:56:25

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

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2017-07-24 01:56:26

Metadata Update from @Firstyear:

• Custom field reviewstatus adjusted to ack (was: review)

[389-ds-bot]

Comment from ilias95 (@ilstam) at 2017-07-28 15:20:08

Metadata Update from @ilstam:

• 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)