Univention Bugzilla – Full Text Bug Listing |
Summary: | S4-Connector syncs back (to_ucs) old group membership of moved users (4.2) | ||
---|---|---|---|
Product: | UCS | Reporter: | Nico Stöckigt <stoeckigt> |
Component: | S4 Connector | Assignee: | Samba maintainers <samba-maintainers> |
Status: | RESOLVED WONTFIX | QA Contact: | Samba maintainers <samba-maintainers> |
Severity: | normal | ||
Priority: | P5 | CC: | best, bremer, gohmann, heidelberger, requate, schwardt, troeder |
Version: | UCS 4.2 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: | https://forge.univention.org/bugzilla/show_bug.cgi?id=56581 | ||
What kind of report is it?: | Bug Report | What type of bug is this?: | 4: Minor Usability: Impairs usability in secondary scenarios |
Who will be affected by this bug?: | 2: Will only affect a few installed domains | How will those affected feel about the bug?: | 3: A User would likely not purchase the product |
User Pain: | 0.137 | Enterprise Customer affected?: | |
School Customer affected?: | Yes | ISV affected?: | |
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | 2018020121000154 | Bug group (optional): | |
Max CVSS v3 score: | |||
Bug Depends on: | 46470, 46682, 46971, 47104, 47636 | ||
Bug Blocks: |
Description
Nico Stöckigt
2018-03-19 12:01:50 CET
From the logs this looks very similar to Bug 46682: univention/s4connector/s4/__init__.py", line 1812, in group_members_sync_from_ucs But I cannot reproduce *that* bug until now. In UCS@school we have a default of connector/s4/mapping/group/syncmode=write, but user object get synchronized in both ways, and that *may* cause group sync to get sync'ed back. The connector-s4.log file shows "sync to ucs" for the affected user objects. But I cannot reproduce it. Additionally to the steps of Bug 46682 Comment 1 I've stopped the notifier on the master before performing the steps and started it later again. All modifications replicated successfully. I think we should first try to fix Bug 46682. I guess that would fix this one too. As Stefan pointed out, the situation of this Ticket #2018020121000154 is more complex because there is an additional AD-Connector involved. This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you. |