Description of problem: Overcloud deployment with external load balancer fails Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-0.8.14-1.el7ost.noarch How reproducible: Steps to Reproduce: 1. Deploy overcloud with external load balancer Actual results: Deployment fails with: [2016-03-31 11:29:04,061] (heat-config) [DEBUG] ++ systemctl is-active pacemaker + pacemaker_status=active ++ hiera bootstrap_nodeid ++ facter hostname ++ hiera update_identifier + '[' active = active -a overcloud-controller-0 = overcloud-controller-0 -a nil '!=' nil ']' + '[' active = active ']' + systemctl reload haproxy Job for haproxy.service invalid. [root@overcloud-controller-0 heat-admin]# systemctl status haproxy ● haproxy.service - HAProxy Load Balancer Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled; vendor preset: disabled) Active: inactive (dead) Mar 31 11:29:04 overcloud-controller-0.localdomain systemd[1]: Unit haproxy.service cannot be reloaded because it is inactive. Expected results: Deployment succeeds Additional info:
this should be fixed when i do the next rebase, it will be addressed by the linked patch. we ended up removing the systemctl reload haproxy in favor of setting UpdateIdentifier, and in that case the haproxy restart is guarded by: if pcs status | grep haproxy-clone; then pcs resource restart haproxy-clone fi so this should resolve the issue with external loadbalancers.
openstack-tripleo-heat-templates-0.8.14-7.el7ost.noarch successfully deployed ha+ex-lb
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0637.html