Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-7792

haproxy : Balance members incorrectly removed

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: haproxy
    • Labels:
    • Environment:

      Description

      Basic Info
      Module Version: 2.1.0
      Puppet Version: Community 5.5
      OS Name/Version: CentOS 7.5

      Using exported resources to define haproxy::balancemember. Initial run on the proxy server creates the balancer as expected with all balance members present. If you run puppet again on the proxy in 10-15 minutes, node 1 and/or node 4 will be removed. Eventually both nodes are removed while the other nodes (2, 3 and 5) are never removed. Server node and proxy definition files attached below. This is happening in both our Production and Development DB cluster environments. Always nodes 1 and 4 that are removed.

      Desired Behavior: ALL Balance Members remain across puppet runs

      Actual Behavior: Node 1 and 4 are removed as Balance Members.

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              johnsmith John W Smith
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Zendesk Support