Alex Schultz 45dcd0e5a8 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 Rocky, we use ntp instead of chrony. Change-Id: I294eba826b98c5793336815282f766e3d2e60a51 Related-Bug: #1776869 (cherry picked from commit eafe390853)		2019-05-23 08:16:41 -06:00
..
conntectx3_streering.yaml	Change template names to rocky	2018-05-09 08:28:42 +02:00
os-net-config-mappings.yaml	Handle upper and lower case system uuids	2019-02-21 19:25:04 +00:00
userdata_default.yaml	Change template names to rocky	2018-05-09 08:28:42 +02:00
userdata_dev_rsync.yaml	Change template names to rocky	2018-05-09 08:28:42 +02:00
userdata_example.yaml	Change template names to rocky	2018-05-09 08:28:42 +02:00
userdata_heat_admin.yaml	Change template names to rocky	2018-05-09 08:28:42 +02:00
userdata_root_password.yaml	Change template names to rocky	2018-05-09 08:28:42 +02:00
userdata_timesync.yaml	Try a timesync as part of first boot	2019-05-23 08:16:41 -06:00