Bug 45171 – Searching for the domain controller master in the system setup returns incorrect results

Bug 45171 - Searching for the domain controller master in the system setup returns incorrect results


Summary:	Searching for the domain controller master in the system setup returns incorr...

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:	45170
Blocks:
	Show dependency tree / graph

Reported:	2017-08-08 18:46 CEST by Tobias Birkefeld
Modified:	2018-07-04 12:52 CEST (History)
CC List:	1 user (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?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.154
Enterprise Customer affected?:	Yes
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 Tobias Birkefeld

2017-08-08 18:46:40 CEST

Also relevant in UCS 4.1 for the customer

+++ This bug was initially created as a clone of Bug #45170 +++

During an installation in the system setup the searching for the domain controller master provides incorrect and incomprehensible results.

The environment has an external non-UCS DNS Server. The SRV Record _domaincontroller_master._tcp."ldap_base" is set correct to the master. Also the FQDN of the DNS Server provide the correct domain part.
But the system setup only set the FQDN of the first DNS server which is configured during the system setup as the proposed domain controller master. There should be a dns lookup of the SRV _domaincontroller_master._tcp."ldap_base" (use function is_ucs_domain from univention-system-setup/umc/python/setup/util.py)

Reproducible intern with antilop as DNS server in the system setup of an UCS Backup/Slave or Member.

Comment 1 Arvid Requate

2018-07-04 12:52:04 CEST

This issue has been filed against UCS 4.1.

UCS 4.1 is out of maintenance and many UCS components have vastly changed in
later releases. Thus, this issue is now being closed.

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