tripleo-heat-templates/firstboot
Alex Schultz 35fc35bc1f Try a timesync as part of first boot
We're running into issues where if someone creates a firstboot script
that touches a file that will eventually be mounted into a container, it
can fail if the time of the file ends up being in the future due to a
later timesync. Let's try a basic timesync bootstrap as part of
cloud-init to address the case of configuration changes occuring prior
to the host_prep_tasks where we traditionally configure chrony/ntp

NOTE: For queens, the overcloud.j2.yaml change lives in
puppet/role.role.j2.yaml. Also we use ntp instead of chrony.

Conflicts:
	overcloud.j2.yaml

Change-Id: I294eba826b98c5793336815282f766e3d2e60a51
Related-Bug: #1776869
(cherry picked from commit eafe390853)
2019-05-23 08:18:40 -06:00
..
conntectx3_streering.yaml Adding a workaround for enabling steering in ConnectX-3 devices 2018-03-08 07:40:49 +00:00
os-net-config-mappings.yaml Handle upper and lower case system uuids 2019-02-21 12:29:16 -07:00
userdata_default.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
userdata_dev_rsync.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
userdata_example.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
userdata_heat_admin.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
userdata_root_password.yaml Change template names to queens 2017-11-23 10:15:32 +01:00
userdata_timesync.yaml Try a timesync as part of first boot 2019-05-23 08:18:40 -06:00