Bug 1287624
Summary: | HA | External LB | Can't deploy HA with external LB because we don't have any haproxy resource to restart when deploying with external lb | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Leonid Natapov <lnatapov> |
Component: | openstack-tripleo-heat-templates | Assignee: | Giulio Fidente <gfidente> |
Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 (Kilo) | CC: | bperkins, calfonso, dnavale, gfidente, johfulto, jslagle, jstransk, kbasil, mburns, mcornea, obaranov, oblaut, rhel-osp-director-maint, ushkalim, yeylon |
Target Milestone: | y2 | Keywords: | Triaged |
Target Release: | 7.0 (Kilo) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-0.8.6-86.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Previously, when piloting the Pacemaker services restart we tried to disable the haproxy clone resource which does not exist when the user configured the overcloud to use an external load balancer. The resulting deployment failed.
With this update, a conditional was added so that restart of the haproxy is skipped if such a response does not exist in the Pacemaker. As a result, the deployment completes successfully as the restart of the haproxy clone is only attempted if the resources exists in the Pacemaker.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-21 16:53:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Leonid Natapov
2015-12-02 13:12:35 UTC
openstack-tripleo-heat-templates-0.8.6-87.el7ost Successfully deployed. 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://access.redhat.com/errata/RHSA-2015:2650 |