Bug 50764 - Joinscript of master meta package is also executed on DC backup
Joinscript of master meta package is also executed on DC backup
Status: NEW
Product: UCS@school
Classification: Unclassified
Component: Metapackages
UCS@school 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-01-31 16:41 CET by Sönke Schwardt-Krummrich
Modified: 2023-06-23 13:43 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
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 2020-01-31 16:41:54 CET
The package ucs-school-master contains a joinscript which is not only executed on the DC master but also on DC backup systems. Since the joinscript does not check whether e.g. the corresponding changes have already been made on the master, they are repeated on the backup if necessary, which can lead to irritation and misconfiguration after installation/update of an additional DC backup.

So far I have identified the following 2 points:
1) append_ucr_policy_to_base should only have an effect on the DC master or be allowed to be executed there.

2) The creation of a demo school also happens on a DC backup via the joinscript. The documentation should clearly state that ucsschool/join/create_demo=no should not only be set on the master, but also on the backups using a UCR policy, so that the behavior in the Backup2Master case is consistent. Also, the code path for creating a demo school on a DC backup should not react at all. This is the task of the DC Master.