Bug 47043 - Add Samba/AD USN Rollback detection script to USI
Add Samba/AD USN Rollback detection script to USI
Status: NEW
Product: USI
Classification: Unclassified
Component: univention-support-info
unspecified
Other Linux
: P5 normal
: ---
Assigned To: USI maintainer
https://support.microsoft.com/en-us/h...
:
Depends on: 47042 47041
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-22 19:34 CEST by Arvid Requate
Modified: 2018-10-18 07:39 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Development Internal
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: 2018052221000458
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 Arvid Requate univentionstaff 2018-05-22 19:34:52 CEST
We should adjust the USI tool to detect a USN rollback in Samba/AD.


+++ This bug was initially created as a clone of Bug #47042 +++

We should also add a UMC Diagnostic check for the situation described below.

+++ This bug was initially created as a clone of Bug #47041 +++

In case a customer has more than one Samba/AD domain controller and he reverts one of them to an earlier VM snapshot (or restores from backup), the AD DRS replication mechanism is broken: All remaining DCs stop receiving changes from the reverted DC until his "highestCommittedUSN" has reached the number that it head before the revert happened.

Since these cases are not very obvious every day error conditions, we should have a Nagios check for that.