Memberof plugin updates group members to add 'memberof' attribute. It case of schema violation, it adds the 'memberOfAutoAddOC' objectclass to the member and retry. If after adding 'memberOfAutoAddOC' it fails again it propagates the schema violation but at some point the return code is lost and not reported. As a consequence not all members have 'memberof' attribute
At least since 1.3.6
testcase provided
When the update on members is failing, the triggering update of the group succeeds
When the update on members is failing, the triggering update of the group should fail
Metadata Update from @tbordaz: - Issue assigned to tbordaz
I thought this would dhave been corrected by having the autoaddOC always a valid OC? Should we do a schema check on the config validation step so we never get an invalid state, and we require always having an OC (such as nsMemberOf)?
Metadata Update from @firstyear: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
@firstyear, autoaddOC works just fine. I used it as a fault injector.
Adding an incorrect OC triggers an error and surprisingly addition of memberof fails but the external update (add a member) succeeds. The problem is that the failure is not propagated.
So ... how do we trigger this then? It sounds like adding an incorrect autoAddOC is the issue here somehow, so is there some validation step we miss? Maybe we need a simple lib389 test so I can understand the problem better. Either way, I think we should fix it ;)
<img alt="ticket49985_test.py" src="/389-ds-base/issue/raw/files/c8dfd07242837d03ad721c3bac9c76acf0f7a4573ab0f43a23ad718d31c9a75e-ticket49985_test.py" />
https://pagure.io/389-ds-base/pull-request/49986
ab4af68..a06c232 master
@tbordaz - can you please cherry pick this to 1.3.9 ?
94378b9..3f8221c 389-ds-base-1.3.9
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.9
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @tbordaz: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1710961
Issue linked to Bugzilla: Bug 1710961
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/3044
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: fixed)
Login to comment on this ticket.