Do not set cluster in maintenance mode during split stack upgrade
authorMarius Cornea <mcornea@redhat.com>
Fri, 20 Oct 2017 08:20:50 +0000 (10:20 +0200)
committerMarius Cornea <mcornea@redhat.com>
Wed, 8 Nov 2017 18:23:25 +0000 (18:23 +0000)
This change noops ControllerDeployedServer{Pre,Post}Config to avoid
getting the upgrade of a split stack deployment getting stuck due
to the cluster being in maintenance mode. For reference a similar
change has been done for the regular Controller role in:
https://review.openstack.org/#/c/487313/

Change-Id: Idd393011b3c4d0d236780e11a04a59d426750de1
Closes-bug: 1725175
(cherry picked from commit 8e92d7c6db6fcae863a250f63b01a98f7a3f3340)

environments/deployed-server-pacemaker-environment.yaml

index cc9ea99..83d81bb 100644 (file)
@@ -1,4 +1,4 @@
 resource_registry:
-  OS::TripleO::Tasks::ControllerDeployedServerPreConfig: ../extraconfig/tasks/pre_puppet_pacemaker.yaml
-  OS::TripleO::Tasks::ControllerDeployedServerPostConfig: ../extraconfig/tasks/post_puppet_pacemaker.yaml
+  OS::TripleO::Tasks::ControllerDeployedServerPreConfig: OS::Heat::None
+  OS::TripleO::Tasks::ControllerDeployedServerPostConfig: OS::Heat::None
   OS::TripleO::Tasks::ControllerDeployedServerPostPuppetRestart: ../extraconfig/tasks/post_puppet_pacemaker_restart.yaml