From 1d7231aae2b523c249da8bada3d33c889c94abb9 Mon Sep 17 00:00:00 2001 From: Michele Baldessari Date: Sat, 1 Oct 2016 17:42:54 +0200 Subject: Change the rabbitmq ha policies during an M/N Upgrade This takes care of the M->N upgrade path when changing the ha rabbitmq policy. Partial-Bug: #1628998 Change-Id: I2468a096b5d7042bc801a742a7a85fb1521c1c02 --- extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh') diff --git a/extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh b/extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh index d4200e5f..23074fcb 100755 --- a/extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh +++ b/extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh @@ -20,9 +20,13 @@ check_disk_for_mysql_dump STONITH_STATE=$(pcs property show stonith-enabled | grep "stonith-enabled" | awk '{ print $2 }') pcs property set stonith-enabled=false -# Migrate to HA NG +# Migrate to HA NG and fix up rabbitmq queues +# We fix up the rabbitmq ha queues after the migration because it will +# restart the rabbitmq resource. Doing it after the migration means no other +# services will be restart as there are no other constraints if [[ -n $(is_bootstrap_node) ]]; then migrate_full_to_ng_ha + rabbitmq_mitaka_newton_upgrade fi # After migrating the cluster to HA-NG the services not under pacemaker's control -- cgit 1.2.3-korg