From 1bfc817f65282ba0cb305aee74caf60165832df4 Mon Sep 17 00:00:00 2001
From: Serguei Bezverkhi <sbezverk@cisco.com>
Date: Fri, 8 Jul 2016 14:03:35 -0400
Subject: [PATCH] Removing .erlang.cookie before rabbitmq bootstrap recreates
 it

In kolla-kubernetes environment rabbitmq bootstrap process fails when
.erlang.cookie already exists, the issue is consistently reproduced when
using persistent storage PV/PVC. This PS prevents this type of failure.

TrivialFix

Change-Id: I3509650b1c11aa45cd5ae2d8eea6523201bfb1de
---
 docker/rabbitmq/extend_start.sh | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docker/rabbitmq/extend_start.sh b/docker/rabbitmq/extend_start.sh
index f0b9fd9c41..56d06aaf90 100644
--- a/docker/rabbitmq/extend_start.sh
+++ b/docker/rabbitmq/extend_start.sh
@@ -4,6 +4,13 @@
 # of the KOLLA_BOOTSTRAP variable being set, including empty.
 if [[ "${!KOLLA_BOOTSTRAP[@]}" ]]; then
     sudo chown -R rabbitmq: /var/lib/rabbitmq
+
+# NOTE(sbezverk): In kubernetes environment, if this file exists from previous
+# bootstrap, the system does not allow to overwrite it (it bootstrap files with
+# permission denied error) but it allows to delete it and then recreate it.
+    if [[ -e "/var/lib/rabbitmq/.erlang.cookie" ]]; then
+        rm -f /var/lib/rabbitmq/.erlang.cookie
+    fi
     echo "${RABBITMQ_CLUSTER_COOKIE}" > /var/lib/rabbitmq/.erlang.cookie
     chmod 400 /var/lib/rabbitmq/.erlang.cookie
     exit 0