Description of problem:
An OCP+CNS 3.9 setup was created usin advanced installation(ansible) deployment. Ansible file had "openshift_clock_enabled=true" option set and hence we expected NTP to be installed and enabled on each of the participating nodes.
But it is seen that all the Nodes, including nodes on which gluster pods are running, do not have any NTP service installed and enabled. Rather "CHRONY" process is seen to be running for time synchronization.
But in all gluster pods, we have NTP process in running state.
Hence, wanted to confirm what is the need for two different time synchronization agents and shouldn't it be better to have single type of process, say NTP process, for both nodes and gluster pods.
Gluster pods always come with NTP by default and for the nodes, we are seeing chrony process running.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install OCP+CNS using Ansible playbook, with "openshift_clock_enabled=true" setting included in file.
2. Check the process running on both gluster nodes and gluster pods.
3. Checked that chrony is running on nodes and NTP on gluster pods, intead of similar process on both.
The gluster nodes and pods have different time synchronization processes instead of a common type
It would be easy if similar process type is used for both so as to have no time related discrepancies.
NTP removed from gluster pods.
Also, NTP service(ntpd/chrony) is started in gluster nodes.
By default, all openshift nodes will have NTP service configured.
Corresponding upstream patches:
Updated doc text in the Doc Text field. Please review for technical accuracy.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.