Bug 56576 – Diagnostic module complains that a user of the limbo school is not a member of any school class

Bug 56576 - Diagnostic module complains that a user of the limbo school is not a member of any school class


Summary:	Diagnostic module complains that a user of the limbo school is not a member o...

Status:	NEW

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - System diagnostic
Version:	UCS@school 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2023-09-13 07:13 CEST by Stefan Gohmann
Modified:	2023-09-13 13:03 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	2: Will only affect a few 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.114
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2023091121000283
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Gohmann

2023-09-13 07:13:34 CEST

The diagnostic module in UMC complains that a user in the limbo / transfer school is not part of any school class. That is wrong because it is the intension of the limbo / transfer school that the user is not part of any class.

Comment 1 Daniel Tröder

2023-09-13 09:39:57 CEST

The name of the limbo-OU needs to be available domain-wide.
It should be moved from the import configuration to DCD.

Comment 2 Sönke Schwardt-Krummrich

2023-09-13 12:44:41 CEST

(In reply to Daniel Tröder from comment #1)
> The name of the limbo-OU needs to be available domain-wide.
> It should be moved from the import configuration to DCD.

Hint 1: IIRC it is possible to have multiple limbo OUs, e.g. one for teachers, one for students → so it's not "the" limbo OU

Hint 2: would be nice, to identify the limbo OU by some kind of LDAP flag → e.g. ucsschoolRole=limbo_ou:school:-

Question to the implementers: do we need the limbo OU in the DCD? Or would a LDAP flag be sufficient for all use cases?

Comment 3 Daniel Tröder

2023-09-13 13:03:44 CEST

- It's only 1 OU for all user roles.
- I like the idea of using "ucsschoolRole" on the OU object. But the question would be how the operator can set it.