From 02f543e0113e1a63f0779974ba7320fc376fb894 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Romain=20Tarti=C3=A8re?= <romain@blogreen.org>
Date: Wed, 30 Jun 2021 16:24:44 -1000
Subject: [PATCH] Explicitly manage /var/run/chrony

We are experiencing CI failures on CentOS because the service cannot
start because it cannot create it's PID file.

Running the very same test locally works as expected, so the root cause
of the different behavior on the CI is unfortunately unknown.  Yet,
ensuring the directory for the PID file exist seems to fix the CI issue.
---
 manifests/config.pp | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/manifests/config.pp b/manifests/config.pp
index a09073b..e2dbae1 100644
--- a/manifests/config.pp
+++ b/manifests/config.pp
@@ -60,4 +60,8 @@
     mode    => $config_keys_mode,
     content => Sensitive(epp($config_keys_template)),
   }
+
+  file { '/var/run/chrony':
+    ensure => directory,
+  }
 }