From 2576acbb897fd077e336a5bc472a6015ee04d328 Mon Sep 17 00:00:00 2001 From: Emilien Macchi Date: Tue, 29 Nov 2016 16:57:20 -0500 Subject: [PATCH] pacemaker: create Mysql_user once Galera is ready (puppet4) Puppet 4 ordering make things more strict in catalog, which is good. Resources have to be orchestrated or Puppet will take them in the order they are found in catalog. This patch makes sure we create MySQL users only when Galera is actually ready. Closes-Bug: #1645787 Change-Id: I536a1a128c3a7eca49bcc4f34a1307bcd60b029e (cherry picked from commit f101ee540a450d3509e1c97aab00a97a2ecf8164) --- manifests/profile/pacemaker/database/mysql.pp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/manifests/profile/pacemaker/database/mysql.pp b/manifests/profile/pacemaker/database/mysql.pp index ad3958371..d3d87e951 100644 --- a/manifests/profile/pacemaker/database/mysql.pp +++ b/manifests/profile/pacemaker/database/mysql.pp @@ -155,9 +155,10 @@ class tripleo::profile::pacemaker::database::mysql ( user => 'clustercheck@localhost', } - # We create databases for services at step 2 as well. This ensures + # We create databases and users for services at step 2 as well. This ensures # Galara is up before those get created Exec['galera-ready'] -> Mysql_database<||> + Exec['galera-ready'] -> Mysql_user<||> } # This step is to create a sysconfig clustercheck file with the root user and empty password