openstack/tripleo-heat-templates
Code Issues Proposed changes

Add fixup for pcs order constraints after update to new templates

Browse Source 
In https://review.openstack.org/#/c/248572/ yum_update.sh
sets the pcs constraints before restarting the cluster. However
after post-update pacemaker run, the previous constraint of
neutron-server...neutron-ovs-cleanup is re-added. Explicitly
remove this before the post-update restart of certain services

Change-Id: I84dd650dcc66ce3f48926cf369b7d691014c2254
This commit is contained in:
marios 2015-11-23 20:10:45 +02:00 committed by Jiri Stransky
parent 0df1c15898
commit 8abee0148d
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
extraconfig/tasks/pacemaker_resource_restart.sh
View File

@ -41,6 +41,12 @@ if [ "$pacemaker_status" = "active" -a \
"$(hiera bootstrap_nodeid)" = "$(facter hostname)" -a \
"$(hiera update_identifier)" != "nil" ]; then
#ensure neutron constraints like
#https://review.openstack.org/#/c/245093/
if pcs constraint order show | grep "start neutron-server-clone then start neutron-ovs-cleanup-clone"; then
pcs constraint remove order-neutron-server-clone-neutron-ovs-cleanup-clone-mandatory
fi
pcs resource disable httpd
check_resource httpd stopped 300
pcs resource disable openstack-keystone