Bug 55035 – Template dhcp.conf using @%@hostname@%@ for ldap-dhcp-server-cn breaks isc-dhcp-server.service

Bug 55035 - Template dhcp.conf using @%@hostname@%@ for ldap-dhcp-server-cn breaks isc-dhcp-server.service


Summary:	Template dhcp.conf using @%@hostname@%@ for ldap-dhcp-server-cn breaks isc-dh...

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Update - univention-updater
Version:	UCS 5.0
Hardware:	amd64 Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2022-07-26 21:10 CEST by Erich
Modified:	2022-08-29 18:31 CEST (History)
CC List:	2 users (show)

See Also:	55032
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?:	4: Will affect most installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.229
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 Erich 2022-07-26 21:10:11 CEST

On upgrading the Domain Master --> Primary, 4-4.9 --> 5.0, the dhcp service failed to launch.

A temporary vim edit of /etc/dhcp/dhcpd.conf:

ldap-server "ucs-9412.grrr.com";
#ldap-dhcp-server-cn "ucs-9412";
ldap-dhcp-server-cn "ucs-9412.grrr.com";
ldap-username "cn=ucs-9412,cn=dc,cn=computers,dc=grrr,dc=com";
ldap-password-file "/etc/machine.secret";
ldap-port 7389;
ldap-base-dn "cn=dhcp,dc=grrr,dc=com";
ldap-method dynamic;


enable the service to start successfully. 

It appears, in this case, that the FQDN is required in order to satisfy a dependency.

I've modified the template file in the interim.

Comment 1 Florian Best

2022-08-26 17:04:57 CEST

Can you provide the error messages of the service start failure?

Comment 2 Erich 2022-08-26 17:52:55 CEST

Just the generic output - not terribly helpful:

Jul 25 06:39:12 ucs-9412 dhcpd[1761]: Configuration file errors encountered – exiting
Jul 25 06:39:12 ucs-9412 dhcpd[1761]:
Jul 25 06:39:12 ucs-9412 systemd[1]: isc-dhcp-server.service: Control process exited, code=exited, status=1/FAILURE
Jul 25 06:39:12 ucs-9412 dhcpd[1761]: If you think you have received this message due to a bug rather
Jul 25 06:39:12 ucs-9412 systemd[1]: isc-dhcp-server.service: Failed with result ‘exit-code’.
Jul 25 06:39:12 ucs-9412 dhcpd[1761]: than a configuration issue please read the section on submitting
Jul 25 06:39:12 ucs-9412 systemd[1]: Failed to start ISC DHCP Server for IPv4.
Jul 25 06:39:12 ucs-9412 dhcpd[1761]: bugs on either our web page at www.isc.org or in the README file
Jul 25 06:39:12 ucs-9412 dhcpd[1761]: before submitting a bug. These pages explain the proper
Jul 25 06:39:12 ucs-9412 dhcpd[1761]: process and the information we find helpful for debugging.
Jul 25 06:39:12 ucs-9412 dhcpd[1761]:
Jul 25 06:39:12 ucs-9412 dhcpd[1761]: exiting.


I took an educated guess that it needed the FQDN versus hostname in the conf file.