From 33e63c2c77fde0af65e33d404dc99036785ee94a Mon Sep 17 00:00:00 2001 From: James Slagle Date: Mon, 3 Apr 2017 12:50:45 -0400 Subject: Purge initial firewall for deployed-server's We need to purge the initial firewall for deployed-server's, otherwise if you have a default REJECT rule, the pacemaker cluster will fail to initialize. This matches the behavior done when using images, see: Iddc21316a1a3d42a1a43cbb4b9c178adba8f8db3 I0dee5ff045fbfe7b55d078583e16b107eec534aa Change-Id: Ia83d17b609e4f737074482a980689cc57c3ad911 Closes-Bug: #1679234 (cherry picked from commit a216934f408439e77bf8346dafe30c4752c70946) --- .../notes/deployed-server-firewall-purge-9d9fe73faf925056.yaml | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 releasenotes/notes/deployed-server-firewall-purge-9d9fe73faf925056.yaml (limited to 'releasenotes/notes') diff --git a/releasenotes/notes/deployed-server-firewall-purge-9d9fe73faf925056.yaml b/releasenotes/notes/deployed-server-firewall-purge-9d9fe73faf925056.yaml new file mode 100644 index 00000000..298a8ece --- /dev/null +++ b/releasenotes/notes/deployed-server-firewall-purge-9d9fe73faf925056.yaml @@ -0,0 +1,6 @@ +--- +fixes: + - The initial firewall will now be purged by the deployed-server bootstrap + scripts. This is needed to prevent possible issues with bootstrapping the + initial Pacemaker cluster. See + https://bugs.launchpad.net/tripleo/+bug/1679234 -- cgit 1.2.3-korg