commit dfdecba88e4508adc50caa7469075e6f42f01468
author Vasyl Saienko <vsaienko@mirantis.com> Fri Oct 13 10:00:57 2023 +0000
committer Vasyl Saienko <vsaienko@mirantis.com> Fri Oct 13 12:24:53 2023 +0000
tree 7b6e0d3479466b47fae0c73f8d1127064381b25a
parent f7b80300ac68f8326cb82d118e8ff8169f09e0ce

Workaround swarm init

Restart docker after swarm init to workaround issue with iptables chain loss.

Change-Id: I2e1f8b26c7b9249ba45262a2649c2c203148bdf7
Related-Prod: PRODX-3456

de/heat-templates/scripts/instance_boot.sh

diff --git a/de/heat-templates/scripts/instance_boot.sh b/de/heat-templates/scripts/instance_boot.sh
index 17a4cab..3ad3f7f 100644
--- a/de/heat-templates/scripts/instance_boot.sh
+++ b/de/heat-templates/scripts/instance_boot.sh
@@ -495,6 +495,10 @@
         echo "This node is already part of a swarm"
     else
         docker swarm init --advertise-addr ${UCP_IP_ADDRESS} --data-path-addr ${UCP_IP_ADDRESS} --listen-addr ${UCP_IP_ADDRESS} --data-path-port ${UCP_DOCKER_SWARM_DATA_PORT}
+        # on 5.15 kernel we loose iptables chains with swarm init, restart docker to workaround this issue.
+        sleep 5
+        systemctl restart docker
+        sleep 5
     fi
 }