Bug 37880

Summary:	Joining into AD domain can be confusing if an old DC master service record exists in the DNS
Product:	UCS	Reporter:	Alexander Kläser <klaeser>
Component:	UMC - Setup wizard	Assignee:	UMC maintainers <umc-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P5	CC:	best, damrose, gohmann
Version:	UCS 4.0
Target Milestone:	UCS 4.0-x
Hardware:	Other
OS:	Linux
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=41796 https://forge.univention.org/bugzilla/show_bug.cgi?id=40342 https://forge.univention.org/bugzilla/show_bug.cgi?id=36413
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:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):	Usability
Max CVSS v3 score:

Description Alexander Kläser

2015-02-25 13:08:35 CET

In the following scenario, joining into an AD domain can confusing:

* An old DC master service record (e.g., from previous test) exists on the AD DNS server side.

* When setting up a new UCS system to join the AD domain, the old DC master service record is detected and one needs to choose a server role (backup, slave, or member).

* The consecutive join fails, as the presumed master does not exist anymore (from setup.log):

**************************************************************************
* Join failed!                                                           *
* Contact your system administrator                                      *
**************************************************************************
__JOINERR__:ping to ucs-7235.mydomain.intranet failed
* Message:  ping to ucs-7235.mydomain.intranet failed
**************************************************************************

We were first a bit puzzled what exactly happened. I can imagine that a tester will have a much harder understanding what exactly has happened.

It would be good at least to prompt a hint in case the presumed DC master cannot be reached. Then, it would be nice to be able to force a join as a DC master and to overwrite existing service records (and maybe other things).

Comment 1 Erik Damrose

2017-05-08 17:27:34 CEST


*** This bug has been marked as a duplicate of bug 41796 ***

Comment 2 Florian Best

2017-11-30 11:46:56 CET


*** This bug has been marked as a duplicate of bug 43745 ***