Hard-coded dependency between haproxy and keepalived

Bug #1642677 reported by Steven Hardy on 2016-11-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Steven Hardy

Bug Description

We hard-code keepalived enabled in the haproxy manifest in puppet-tripleo, which means you can't deploy minimal configurations where keeplived isn't required.

We should instead use the hiera keepalived_enabled to replace the current hard-coded "true"

Steven Hardy (shardy) on 2016-11-17
Changed in tripleo:
importance: Undecided → Low
status: New → In Progress
assignee: nobody → Steven Hardy (shardy)
milestone: none → ocata-2

Reviewed: https://review.openstack.org/399152
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=92f9c952d6cbb0c11c8457de0e49748f3adf667e
Submitter: Jenkins
Branch: master

commit 92f9c952d6cbb0c11c8457de0e49748f3adf667e
Author: Steven Hardy <email address hidden>
Date: Thu Nov 17 17:37:45 2016 +0000

    Replace hard-coded haproxy/keepalived coupling

    We have a variable in hiera which tells us if the keepalived
    service is enabled, so use it here. Without this any deployment
    disabling OS::TripleO::Services::Keepalived will fail.

    Change-Id: I90faf51881bd05920067c1e1d82baf5d7586af23
    Closes-Bug: #1642677

Changed in tripleo:
status: In Progress → Fix Released

This issue was fixed in the openstack/puppet-tripleo 6.1.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers