From 4a97d372341c93fe31a2cc3296a3cdb486000ac3 Mon Sep 17 00:00:00 2001
From: Paul Bourke <paul.bourke@oracle.com>
Date: Thu, 4 May 2017 10:41:18 +0100
Subject: [PATCH] Fix logging for chrony

Chrony drops root to user 'chrony' on startup, and so was unable to
write to its log dir. Apply our usual chown on start pattern to fix
this.

Change-Id: Ia54cf5788ad015c3622902bca810bcbaaa948253
Closes-Bug: #1688216
---
 docker/chrony/extend_start.sh | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/docker/chrony/extend_start.sh b/docker/chrony/extend_start.sh
index 80af48dba9..bc28e56969 100644
--- a/docker/chrony/extend_start.sh
+++ b/docker/chrony/extend_start.sh
@@ -2,9 +2,15 @@
 
 rm -f /var/run/chronyd.pid
 
-if [[ ! -d "/var/log/kolla/chrony" ]]; then
-    mkdir -p /var/log/kolla/chrony
+CHRONY_LOG_DIR="/var/log/kolla/chrony"
+if [[ ! -d "${CHRONY_LOG_DIR}" ]]; then
+    mkdir -p ${CHRONY_LOG_DIR}
 fi
-if [[ $(stat -c %a /var/log/kolla/chrony) != "755" ]]; then
+
+if [[ $(stat -c %a ${CHRONY_LOG_DIR}) != "755" ]]; then
     chmod 755 /var/log/kolla/chrony
 fi
+
+if [[ $(stat -c %U:%G ${CHRONY_LOG_DIR}) != "chrony:chrony" ]]; then
+    chown chrony:chrony ${CHRONY_LOG_DIR}
+fi