Bug 37273 - Extend the domain controller not found message
Extend the domain controller not found message
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Setup wizard
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-12-10 06:28 CET by Stefan Gohmann
Modified: 2019-01-03 07:17 CET (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.103
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

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2014-12-10 06:28:39 CET
Currently, I get the following message if I try to install a slave and a DC wasn't found:

No domain controller was found at the address of the name server. It is recommended to verify that the network settings are correct.

It is unclear what correct means. We should add a hint that in most scenarios the domain controller master should be used as name server. Or at least one of the existing UCS DCs.
Comment 1 Alexander Kläser univentionstaff 2014-12-10 11:53:17 CET

*** This bug has been marked as a duplicate of bug 37263 ***
Comment 2 Alexander Kläser univentionstaff 2014-12-10 12:11:01 CET
(In reply to Alexander Kläser from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 37263 ***

Not really a duplicate, I was too fast.
Comment 3 Stefan Gohmann univentionstaff 2015-03-12 08:27:14 CET
(In reply to Stefan Gohmann from comment #0)
> Currently, I get the following message if I try to install a slave and a DC
> wasn't found:
> 
> No domain controller was found at the address of the name server. It is
> recommended to verify that the network settings are correct.
> 
> It is unclear what correct means. We should add a hint that in most
> scenarios the domain controller master should be used as name server. Or at
> least one of the existing UCS DCs.

Furthermore we should add a hint which DNS records need to be found, for example Bug #37501 for the reverse pointer.

To make it clear, in this bug we should only adjust the messages.
Comment 4 Stefan Gohmann univentionstaff 2015-06-25 07:27:33 CEST
If I see it correctly, this doesn't happen very often. Reset target milestone.
Comment 5 Stefan Gohmann univentionstaff 2019-01-03 07:17:50 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.