From 146398d0b802e412f1eb3b33915ff1532909f606 Mon Sep 17 00:00:00 2001
From: Ben Nemec <bnemec@redhat.com>
Date: Wed, 18 Jul 2018 16:17:27 +0000
Subject: [PATCH] Run designate pool update only on bootstrap node

If this is run on all nodes it can cause collisions while updating
the database.

Change-Id: I1dcb28aac111189eec142c6b4c8879431f72094b
(cherry picked from commit 1fe1798aee8d381548d1af35b92053118d356efb)
---
 docker/services/designate-central.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docker/services/designate-central.yaml b/docker/services/designate-central.yaml
index 6cec04120b..e7d99f2908 100644
--- a/docker/services/designate-central.yaml
+++ b/docker/services/designate-central.yaml
@@ -150,14 +150,14 @@ outputs:
             net: host
             privileged: false
             detach: false
-            user: designate
+            user: root
             volumes:
               list_concat:
                 - {get_attr: [ContainersCommon, volumes]}
                 -
                   - /var/lib/config-data/designate/etc/designate/:/etc/designate/:ro
                   - /var/log/containers/designate:/var/log/designate
-            command: "/bin/designate-manage pool update"
+            command: "/usr/bin/bootstrap_host_exec designate_central su designate -s /bin/bash -c '/bin/designate-manage pool update'"
       host_prep_tasks:
         - name: create persistent logs directory
           file: