Chrony configuration not updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Alberto Donato | ||
2.8 |
Fix Released
|
High
|
Alberto Donato |
Bug Description
Reported from https:/
New insall of MaaS 2.8 (7328) is not respecting the NTP configuration. I have configured my internal NTP servers as a destination, but the server is still reaching out to the default ubuntu pool.
root 10131 0.0 0.0 110356 3220 ? S 20:11 0:00 /snap/maas/
There is a configuration file which is correct: /var/snap/
Some additional troubleshooting here. When I cat “/var/snap/
After getting everything restarted, I cat’d “/var/snap/
Related branches
- Alberto Donato (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 16 lines (+3/-2)1 file modifiedsnap/local/tree/bin/run-chronyd (+3/-2)
- Adam Collard (community): Approve
- MAAS Lander: Needs Fixing
-
Diff: 16 lines (+3/-2)1 file modifiedsnap/local/tree/bin/run-chronyd (+3/-2)
Changed in maas: | |
milestone: | 2.8.1 → 2.9.0b1 |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Can you please target this to 2.8.2 too?