Fix CrashLoopBackoff in emco-fluentd Pod

The emco-fluentd pod is stuck in CrashLoopBackOff due to a failure to
resolve the "cluster.local" name.  Explicitly set the
fluentd.clusterDomain value to the actual cluster name during helm
install.

Issue-ID: MULTICLOUD-1244
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Ia6424e7ce8d4544511ad88c478e65fa8c4df0c52

diff --git a/kud/deployment_infra/playbooks/configure-emco.yml b/kud/deployment_infra/playbooks/configure-emco.yml
index eb6adcf..7a4cf92 100644 (file)
--- a/kud/deployment_infra/playbooks/configure-emco.yml
+++ b/kud/deployment_infra/playbooks/configure-emco.yml
@@ -36,6 +36,10 @@
     - debug:
         var: make_all.stdout_lines
 
+    - name: Get cluster name
+      shell: "kubectl -n kube-system get configmap/kubeadm-config -o yaml | grep clusterName: | awk '{print $2}'"
+      register: cluster_name
+
     - name: Change the emco directory and run the command helm install
       command: /usr/local/bin/helm install --namespace emco --create-namespace --set emco-tools.fluentd.clusterDomain={{ cluster_name.stdout }} emco dist/packages/emco-0.1.0.tgz
       register: helm_install