Bug 44174 – Domain name server already checked during installation while joining is scheduled for after setup

Bug 44174 - Domain name server already checked during installation while joining is scheduled for after setup


Summary:	Domain name server already checked during installation while joining is sched...

Status:	RESOLVED DUPLICATE of bug 43402

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-31 08:19 CEST by Philipp Hahn
Modified:	2018-04-14 13:37 CEST (History)
CC List:	2 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?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.017
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 Philipp Hahn

2017-03-31 08:19:21 CEST

After a server crash I had to setup my test domain again and started a parallel installation of 1 Master, 1 Backup and 1 Member.
I de-delected 'join domain' on master and member, but after software selection the installation was blocked until the master was ready:

umc/python/setup/__init__.py:517
> _('The specified nameserver %s is not part of a valid UCS domain.'

IMHO that check should not be performed if I de-delect joining the domain.
Or at least provide an expert mode to ignore that check.

Comment 1 Erik Damrose

2017-03-31 09:45:03 CEST

I think this is a duplicate of bug 43402, please confirm

Comment 2 Philipp Hahn

2017-03-31 09:47:55 CEST


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