Bug 33384 – backup2master should not claim all FSMO roles

Bug 33384 - backup2master should not claim all FSMO roles


Summary:	backup2master should not claim all FSMO roles

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	backup2master
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-11-14 15:36 CET by Arvid Requate
Modified:	2020-07-03 20:54 CEST (History)
CC List:	5 users (show)

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:

Flags:	gohmann: Patch_Available+

Attachments
backup2master_differential_fsmo_transfer.patch (1.08 KB, patch) 2013-11-14 15:36 CET, Arvid Requate	Details \| Diff
View All 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 Arvid Requate

2013-11-14 15:36:52 CET

Created attachment 5631 [details]
backup2master_differential_fsmo_transfer.patch

Currently univention-backup2master checks if the old master held any FSMO role, and if that is the case, it transfers all FSMO roles to the new master.

The attached patch changes this to iterate over all five FSMO roles and transfer each of them individually. This needs to be checked, IIRC the order of the FSMOs might be important here.


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

Comment 1 Stefan Gohmann

2017-06-16 20:37:45 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 2 Ingo Steuwer

2020-07-03 20:54:45 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have 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 it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.