Bug 37098 – ntpdate does not honor DHCP configuration

Bug 37098 - ntpdate does not honor DHCP configuration


Summary:	ntpdate does not honor DHCP configuration

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	NTP
Version:	UCS 4.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-28 10:15 CET by Philipp Hahn
Modified:	2019-01-03 07:18 CET (History)
CC List:	1 user (show)

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

2014-11-28 10:15:02 CET

DHCP provides the "option ntp-servers" to configure a NTP server. This is not honored by UCS, where /etc/default/ntpdate and /etc/ntp.conf only support static configuration via UCRV timeserver{,2,3}.

/usr/sbin/ntpdate-debian already has the logic to read /var/lib/ntpdate/default.dhcp, which is updated by /etc/dhcp/dhclient-exit-hooks.d/ntpdate, but is not used - instead we still use plain /usr/sbin/ntpdate with explicitly given NTP servers.

At least for DC Master installation we should honor the DHCP setting as for the master no NTP server is configured by default. All other system roles use the DC Master (UCRV ldap/master) and all other DC Backups (UCRV ldap/backup) by default.

Comment 1 Stefan Gohmann

2019-01-03 07:18:15 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.