From 8972b0c1c4a45cf8fd766faeb0e3db0bcc51354c Mon Sep 17 00:00:00 2001 From: Hongbin Lu Date: Tue, 5 Apr 2016 18:18:06 -0400 Subject: [PATCH] Notify Heat only if kube-apiserver is running Kubernetes bay needs to be fully functional before notifying Heat to bring the stack to CREATE_COMPLETE. This patch added a systemd unit that keeps pinging the kube-apiserver and notify Heat once it goes through. Change-Id: Ib4fb22f3040d76d488c6cac6873d64b4d973ebb1 Closes-Bug: #1551824 --- .../kubernetes/fragments/wc-notify-master.sh | 36 +++++++++++++++++++ magnum/templates/kubernetes/kubemaster.yaml | 8 +---- magnum/tests/contrib/copy_instance_logs.sh | 1 + 3 files changed, 38 insertions(+), 7 deletions(-) create mode 100644 magnum/templates/kubernetes/fragments/wc-notify-master.sh diff --git a/magnum/templates/kubernetes/fragments/wc-notify-master.sh b/magnum/templates/kubernetes/fragments/wc-notify-master.sh new file mode 100644 index 0000000000..1fc8a0d496 --- /dev/null +++ b/magnum/templates/kubernetes/fragments/wc-notify-master.sh @@ -0,0 +1,36 @@ +#!/bin/sh + +. /etc/sysconfig/heat-params + +WC_NOTIFY_BIN=/usr/local/bin/wc-notify +WC_NOTIFY_SERVICE=/etc/systemd/system/wc-notify.service + +cat > $WC_NOTIFY_BIN < $WC_NOTIFY_SERVICE <