Bug 41796 – UCS Join against AD - Role Warning if first join failed

Bug 41796 - UCS Join against AD - Role Warning if first join failed


Summary:	UCS Join against AD - Role Warning if first join failed

Status:	RESOLVED DUPLICATE of bug 43745

Product:	UCS
Classification:	Unclassified
Component:	System setup
Version:	UCS 4.1
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-07-15 07:41 CEST by Jens Thorp-Hansen
Modified:	2018-04-14 13:37 CEST (History)
CC List:	3 users (show)

See Also:	37880 36413 40342
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.171
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:

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 Jens Thorp-Hansen

2016-07-15 07:41:19 CEST

currently when joining against a AD the UCS will be made "master" and there is no information displayed. Role choice is displayed for all following servers (role choice excludes "master").

If the first join fails, there are often fragments in the environment left - if one just tries to rejoin the "master" anew it will not be possible, since UCS thinks there is already a "master" present.

Could be solved multiple ways I think:

- clean up failed join automatically
- display the server role that will be used (and possibly why) more clearly
- set a dirty-flag on failed join and throw a clear warning if dirty flag is present

Comment 1 Erik Damrose

2017-05-08 17:27:34 CEST

*** Bug 37880 has been marked as a duplicate of this bug. ***

Comment 2 Florian Best

2017-11-30 11:47:03 CET


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