Bug 50038 - backup2master: describe risks about potential newer defaults
backup2master: describe risks about potential newer defaults
Status: NEW
Product: UCS manual
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Docu maintainers
Docu maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-08-21 16:57 CEST by Ingo Steuwer
Modified: 2019-08-21 17:10 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
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:
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 Ingo Steuwer univentionstaff 2019-08-21 16:57:52 CEST
Scenario:

* DC Master has been installed a few years ago
* DC Backup has been installed yesterday
* DC Backup is promoted to DC Master using "backup2master"

As we change some UCR settings and other defaults only for newly installed machines, the configuration and therefore behavior of the new DC Master might be different from the DC Backup. We should describe the risk in the documentation and give some hints how to mitigate them (i.e. compare "ucr dump").

One Example: newer installations of univention-s4-connector add attributes to the mapping.
Comment 1 Erik Damrose univentionstaff 2019-08-21 17:10:32 CEST
Additional note about the example: For package based Apps the App Center will install e.g. schema extension packages on DC Backups during app installation. They will be missing if the DC Backup was 'just' added.