PR#50144: Ticket 50078 - cannot add cenotaph in read only consumer -

389-ds-base

#50144 Ticket 50078 - cannot add cenotaph in read only consumer

Closed Sep 13, 2020 by spichugi. Opened Jan 10, 2019 by lkrispen.

lkrispen/389-ds-base t50078 into master

lkrispen commented Jan 10, 2019

Bug: For modrdn operations a cenotaph entry is created to be used in later conflict
resolution procedures, this is done by an internal add operation and
fails on hubs and consumers

Fix: Add the "bypass referral" flag to the internal add operation to allow it

Reviewed by: ?

tbordaz commented Jan 10, 2019

The patch looks good. Ack

rebased onto 83223d5f008c47cf01450a21a6e74f1916b9a5a1

Jan 10, 2019

Pull-Request has been merged by lkrispen

Jan 10, 2019

firstyear commented Feb 13, 2019

All looks great to me, ack,

spichugi commented Sep 13, 2020

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3203

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi

Sep 13, 2020

Metadata

Assignee

None

Tags

No Tags

389-ds-base

#50144 Ticket 50078 - cannot add cenotaph in read only consumer Closed Sep 13, 2020 by spichugi. Opened Jan 10, 2019 by lkrispen. lkrispen/389-ds-base t50078 into master

Metadata

#50144 Ticket 50078 - cannot add cenotaph in read only consumer

Closed Sep 13, 2020 by spichugi. Opened Jan 10, 2019 by lkrispen.

lkrispen/389-ds-base t50078 into master