Bug 40342 – Show an info about the existing UCS master in the AD DNS

Bug 40342 - Show an info about the existing UCS master in the AD DNS


Summary:	Show an info about the existing UCS master in the AD DNS

Status:	RESOLVED DUPLICATE of bug 43745

Product:	UCS
Classification:	Unclassified
Component:	UMC - Setup wizard
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 4.1-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-12-28 08:13 CET by Stefan Gohmann
Modified:	2017-11-30 11:21 CET (History)
CC List:	4 users (show)

See Also:	37880 36413 41796
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):
Max CVSS v3 score:

Attachments
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 Stefan Gohmann

2015-12-28 08:13:54 CET

If UCS joins into an Active Directory domain, the first UCS system registers itself in the DNS of the Active Directory domain.

We should show an info if the second UCS system joins into the Active Directory domain. The info should explain the situation.

It seems to happen often that the first UCS system is only a test system and the second system is the "real" UCS system.

Comment 1 Jens Thorp-Hansen

2016-01-06 17:18:30 CET

related/happened again: Ticket#2015121521000445

Comment 2 Alexander Kläser

2016-04-14 17:02:25 CEST

Do we know how often this problem happens? Do we know how often the AD member mode is used?

IMHO this is quite a usability problem which we should fix soon. I am not sure whether a test will be able to resolve the problem by himself.

Comment 3 Florian Best

2017-11-30 11:21:02 CET


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