Description of problem:
Overcloud deployments with external loadbalancer fail:
2016-11-15 02:35:28Z [overcloud.AllNodesDeploySteps]: CREATE_FAILED Error: resources.AllNodesDeploySteps.resources.ControllerPostPuppet.resources.ControllerPostPuppetRestart.resources.ControllerPostPuppetRestartDeployment.resources: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status
2016-11-15 02:35:28Z [overcloud]: CREATE_FAILED Resource CREATE failed: Error: resources.AllNodesDeploySteps.resources.ControllerPostPuppet.resources.ControllerPostPuppetRestart.resources.ControllerPostPuppetRestartDeployment.resources: Deployment to server failed: deploy_status_code: Deployment exi
Stack overcloud CREATE_FAILED
openstack software deployment output show 4f339ca4-7600-4ca0-b0ef-f798bc47b6cf --all
+ [[ -d /var/lib/tripleo/pacemaker-restarts ]]
++ systemctl is-active haproxy
openstack software deployment show 4f339ca4-7600-4ca0-b0ef-f798bc47b6cf
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy overcloud with 3 controllers, 2 compute and an external load balancer
The failure seems to be related to the fiz for BZ#1390962 as in the case of an external load balancer deployment haproxy is not running on the controllers.
On controller nodes:
[root@overcloud-controller-0 ~]# systemctl status haproxy; echo $?
● haproxy.service - HAProxy Load Balancer
Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled; vendor preset: disabled)
Active: inactive (dead)
Marius could you try the (trivial) review I attached here and report back?
(In reply to Michele Baldessari from comment #2)
> Marius could you try the (trivial) review I attached here and report back?
Thanks Michele. I applied it to my environment and deployment passed.
This issue also affects non-ssl to ssl deployment conversion.
https://review.openstack.org/#/c/398040/ merged to stable/newton moving to POST
removing master external reference as stable/newton patch is landed
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.