DHCP-received NTP servers override the configuration of the NTP charm
Bug #1758775 reported by
Paul Gear
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NTP Charm |
Fix Released
|
Medium
|
Haw Loeung |
Bug Description
Example from GCE, but could be seen in MAAS/OpenStack or any other environment where NTP server addresses are supplied via DHCP: https:/
When a user configures NTP with this charm, they should reasonably expect their configuration to be reliably applied rather than overridden by their cloud provider.
Related branches
~hloeung/ntp-charm:master
- Joel Sing (community): Approve (+1)
- Canonical IS Reviewers: Pending requested
-
Diff: 32 lines (+21/-0)1 file modifiedreactive/ntp.py (+21/-0)
Changed in ntp-charm: | |
assignee: | Paul Gear (paulgear) → nobody |
Changed in ntp-charm: | |
assignee: | nobody → Haw Loeung (hloeung) |
status: | Triaged → In Progress |
no longer affects: | ntp (Ubuntu) |
Changed in ntp-charm: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
I intend to integrate a fix for this with the work to enable chrony support for bionic.