Bug 48838 - ucsschoolRole of DC master not updated during migration from singleserver to multiserver
ucsschoolRole of DC master not updated during migration from singleserver to ...
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: LDAP
UCS@school 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-03-03 22:40 CET by Sönke Schwardt-Krummrich
Modified: 2023-06-23 13:15 CEST (History)
0 users

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?: 1: Will affect a very 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.034
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 Sönke Schwardt-Krummrich univentionstaff 2019-03-03 22:40:09 CET
During migration form singleserver to multiserver, the ucsschoolRole of the UCS@school master is not updated. After the update, I found the following values:

dn: cn=master140,cn=dc,cn=computers,dc=nstx,dc=local
cn: master140
ucsschoolRole: dc_master:school:-
ucsschoolRole: single_master:school:-
ucsschoolRole: single_master:school:DEMOSCHOOL
ucsschoolRole: single_master:school:gsmitte
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2019-03-03 22:44:35 CET
Even "./migrate_ucsschool_roles --servers-central --force --modify" does not correct this.
Comment 2 Jan-Luca Kiok univentionstaff 2023-06-23 13:15:30 CEST
This issue has been filed against UCS 4.4.

UCS 4.4 is out of maintenance and UCS components may have vastly 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 this issue. In this case please provide detailed information on how this issue is affecting you.