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
This commit is contained in:
Damien Ciabrini 2016-06-29 22:36:34 +02:00
parent 463333ccc7
commit 017334bbb5
1 changed files with 1 additions and 1 deletions

View File

@ -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"