Ben Nemec 4f373ea30f Restart haproxy after configuring SSL certs ... If a certificate expires, the user will need to update it. However, because we only restart services at the end of a stack-update the new certificate doesn't take effect until after puppet has run. This is a problem because puppet makes OpenStack calls, which will fail if the certificate is expired. In that case we never get to the service restart so the stack is wedged until the user manually restart haproxy. This patch addresses the problem by reloading haproxy before puppet runs. This is done in a pre-puppet script for pacemaker after pacemaker is maintenance mode because we need to make sure it happens after all of the certs have been installed on the controllers, but before puppet runs. For non-pacemaker, haproxy is simply reloaded. Change-Id: Id5ed05b3a20d06af8ae7a3d6f859b03399b0d77d		2016-04-01 12:42:02 -04:00
..
all_nodes	Add an environment to use a swap partition	2016-03-06 16:06:18 -05:00
post_deploy	Set the name property for all deployment resources	2015-12-10 14:48:04 +13:00
pre_deploy/rhel-registration	change the default satellite tools rpm repo.	2016-03-29 12:14:22 -04:00
tasks	Restart haproxy after configuring SSL certs	2016-04-01 12:42:02 -04:00