Bug 49864 - Group membership can be wrong after after a school move
Group membership can be wrong after after a school move
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: Ucsschool-lib
UCS@school 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-07-17 12:23 CEST by Jürn Brodersen
Modified: 2023-10-26 14:37 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.103
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jürn Brodersen univentionstaff 2019-07-17 12:23:20 CEST
Group membership can be wrong after after a school move
Not all old groups are removed after the move (Domain Users $SCHOOL)

The test 80_move_users_into_another_ou is failing (flaky). I think the test is correct and this is an actual bug.

The test failed during a complete move: Student is only in school A and is moved into school B.

The user is moved first and afterwards removed from it's old school groups. It looks like the s4-connector might be readding the old groups because it wasn't done moving the student before the groups were removed through udm.

I think we had similiar problems in ucs@school, but I can't find the bug.
Comment 1 Jan-Luca Kiok univentionstaff 2023-10-26 14:37:38 CEST
This issue has been filed against UCS@school 4.4.

UCS@school 4.4 is out of maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.