Bug 47679 - UCS Memberserver has ldap/server/ip=127.0.0.1 and installing univention-bind fails
UCS Memberserver has ldap/server/ip=127.0.0.1 and installing univention-bind ...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-08-27 15:29 CEST by Arvid Requate
Modified: 2021-05-14 16:34 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
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

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2018-08-27 15:29:48 CEST
On a UCS 4.3-1 Memberserver the UCS variable ldap/server/ip is still set to the default "127.0.0.1", as defined in univention-base-files.postinst.

So in my case I find on master13 (10.200.8.13) these UCR values:

ldap/server/ip: 127.0.0.1
ldap/server/name: master10.ar41i1.qa


If somebody decides to run a DNS server in the UCS Memberserver, then ldap/server/ip is used in /etc/bind/univention.conf.d/* to configure the LDAP connection for univention-bind and that clearly fails (first symptom: 90univention-bind-post.inst takes a long time, because it repeatedly fails to resolve ldap/master against the local nameserver).

We should set ldap/server/ip to match ldap/server/name in this case.
Comment 1 Ingo Steuwer univentionstaff 2021-05-14 15:41:16 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have 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" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.