Allow use of outward rabbitmq even if external vip isn't enabled

Bug #1722854 reported by serlex
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Medium
serlex
Pike
Fix Released
Medium
Unassigned
Queens
Fix Released
Medium
serlex

Bug Description

Hi,

Currently

/usr/share/kolla/ansible/roles/haproxy/templates/haproxy.cfg.j2

Contains

{% if haproxy_enable_external_vip | bool %}

listen outward_rabbitmq_external
  mode tcp
  option tcplog
  timeout client 3600s
  timeout server 3600s
  bind {{ kolla_external_vip_address }}:{{ outward_rabbitmq_port }}
{% for host in groups['outward-rabbitmq'] %}
  server {{ hostvars[host]['ansible_hostname'] }} {{ hostvars[host]['ansible_' + hostvars[host]['api_interface']]['ipv4']['address'] }}:{{ outward_rabbitmq_port }} check inter 2000 rise 2 fall 5
{% endfor %}
{% endif %}

But I want to be able to use outward rabbit with HAproxy even if I haven't enabled haproxy_enable_external_vip

I believe if statement above needs to be changed to enable_outward_rabbitmq

Regards

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/511298
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=d55f2785e30246a64af493d87ac4c05ab0227e74
Submitter: Jenkins
Branch: master

commit d55f2785e30246a64af493d87ac4c05ab0227e74
Author: root <email address hidden>
Date: Wed Oct 11 17:15:33 2017 +0100

    Allow outward_rabbitmq with enable_outward_rabbitmq

    outward_rabbitmq is determined using enable_outward_rabbitmq
    property rather than current haproxy_enable_external_vip

    Change-Id: Iee096ab50fd4d9f5f3fe05880d0e0a7842c59d0a
    Closes-Bug: 1722854

Changed in kolla-ansible:
status: New → Fix Released
serlex (serlex)
Changed in kolla-ansible:
assignee: nobody → serlex (serlex)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 6.0.0.0b2

This issue was fixed in the openstack/kolla-ansible 6.0.0.0b2 development milestone.

Changed in kolla-ansible:
milestone: queens-2 → rocky-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (stable/pike)

Reviewed: https://review.openstack.org/514913
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=6c12a6fd104a7be225f6ddb85e80e7c5c8458a94
Submitter: Zuul
Branch: stable/pike

commit 6c12a6fd104a7be225f6ddb85e80e7c5c8458a94
Author: root <email address hidden>
Date: Wed Oct 11 17:15:33 2017 +0100

    Allow outward_rabbitmq with enable_outward_rabbitmq

    outward_rabbitmq is determined using enable_outward_rabbitmq
    property rather than current haproxy_enable_external_vip

    Change-Id: Iee096ab50fd4d9f5f3fe05880d0e0a7842c59d0a
    Closes-Bug: 1722854
    (cherry picked from commit d55f2785e30246a64af493d87ac4c05ab0227e74)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 5.0.3

This issue was fixed in the openstack/kolla-ansible 5.0.3 release.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.