NTP may fail to sync if explicit time sync is not performed

[Julia Kreger]

Time sensitive services may not be able to startup and be synchronized, specifically when deployed on multiple nodes as opposed to a virtual testing environment, when the hardware clock of the booting system is not explicitly synchronized before attempting to start the services. With this, NTP itself may not be able to synchronize and start operating if the clock is skewed too much from the clock source(s), or if one clock source is out of sync itself.

It is worth pointing out that if the testing VM clock source is not configured correctly, this issue could also potentially be encountered.

Related reading: http://www.ntp.org/ntpfaq/NTP-s-algo-real.htm#Q-NTP-ALGO

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/145737

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/145743

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/145743
Committed: https://git.openstack.org/cgit/openstack/tripleo-image-elements/commit/?id=b8266fa7ecab87a4ae015139e8f8b8a7cd5c714e
Submitter: Jenkins
Branch: master

commit b8266fa7ecab87a4ae015139e8f8b8a7cd5c714e
Author: Nicholas Randon <email address hidden>
Date: Wed Jan 7 09:33:15 2015 +0000

    NTP fail to sync if time sync is not performed

    Time sensitive services may not be able to startup and be synchronized,
    specifically when deployed on multiple nodes, when the hardware clock
    of the booting system is not explicitly synchronized before attempting
    to start the services. With this, NTP itself may not be able to
    synchronize and start operating if the clock is skewed too much from
    the clock source(s), or if one clock source is out of sync itself.

    This change move the ntp stand-up earlier in setup so that time of any
    system is controlled befor time sensitive services startup. For example
    the database on controller nodes. The change also set the clock to the
    time of the given ntp server forcefully and updates the Hardware clock.
    It also fixes the invalid ntp.conf file.

    Closes-Bug: 1408379
    Relates-To: I56a03dc0a899a8c515f2a05d678d7e80e9b7b93c
    Change-Id: Ib9931b84925d9ceb32f18e9adc5be64402fbf61e

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/145737
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=42a3b362479f0f9e55f8f57f7fd6d638e5bf36bf
Submitter: Jenkins
Branch: master

commit 42a3b362479f0f9e55f8f57f7fd6d638e5bf36bf
Author: Nicholas Randon <email address hidden>
Date: Wed Jan 7 18:54:08 2015 +0000

    Remove invalid NTP configuration in templates

    Currently the all templates have an invalid setting for NTP
    setup for the fudge setting. This should be removed from
    the templates which will remove the warning seen in syslog.

    ntpd[...]: inappropriate address xxx.xxx.xxx.xxx for the
        fudge command, line ignored

    Partial-Bug: 1408379
    Relates-To: Ib9931b84925d9ceb32f18e9adc5be64402fbf61e
    Change-Id: I56a03dc0a899a8c515f2a05d678d7e80e9b7b93c