From 017334bbb5978ed9a9c06f4595506612287c1b14 Mon Sep 17 00:00:00 2001 From: Damien Ciabrini Date: Wed, 29 Jun 2016 22:36:34 +0200 Subject: [PATCH] Increase cluster sync timeout for M->N major upgrades Since the Liberty release, the number of services managed by pacemaker on HA Overcloud has increased. This has an impact on major_upgrade_controller_pacemaker_1.sh, where cluster sync timeout value tuned for older releases is now becoming too low. Raise the cluster sync timeout value to a sensible limit to give pacemaker enough time to stop the cluster during major upgrade. Change-Id: I821d354ba30ce39134982ba12a82c429faa3ce62 Closes-Bug: #1597506 --- extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh b/extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh index 72bb81f5..2aaa84c6 100755 --- a/extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh +++ b/extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh @@ -2,7 +2,7 @@ set -eu -cluster_sync_timeout=600 +cluster_sync_timeout=1800 if pcs status 2>&1 | grep -E '(cluster is not currently running)|(OFFLINE:)'; then echo_error "ERROR: upgrade cannot start with some cluster nodes being offline" -- 2.16.6