View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0013549||CentOS-7||chrony||public||2017-07-14 09:30||2017-11-20 20:23|
|Target Version||Fixed in Version|
|Summary||0013549: Chrony depends on default route|
|Description||The script /etc/NetworkManager/dispatcher.d/20-chrony imposes the presence of default route in order to set online the chrony. |
On system without default route, like router, is not so smart
Can we fix it with a parameter in /etc/sysconfig/chrony ?
|Tags||No tags attached.|
I've been attempting to replicate this issue and don't think changes to chrony are required in order to get it to operate the way that you expect.
First, I have confirmed that you do not need to tell chronyd to go online UNLESS chronyd has been told to go offline. When chronyd is first started, all sources default to "doing burst (return to online)" and communication with the sources is attempted.
/etc/NetworkManager/dispatcher.d/20-chrony does tell chrony to go offline if an interface is taken down and there is no default route. ***This will happen in your scenario***
/etc/NetworkManager/dispatcher.d/20-chrony does not tell chrony to go back online unless an interface is brought up and there is a default route. ***This will never happen in your scenario***
chronyd should start when the system boots and attempt to talk to all sources. Unless you have an interface that goes down, the presence or absence of a default route will not change the behavior of chronyd.
I recommend that you remove /etc/NetworkManager/dispatcher.d/20-chrony, or otherwise edit it to work as needed.
An edit that is likely to work for you is to comment out like 8, which checks for a default route when an interface is brought up. But, since all 20-chrony does is manipulate chronyd based on existing or missing default routes when interfaces go up and down, removing the file is probably easier.
-Rich Alloway (Rogue Wave)