fluentd output to elasticsearch should use elasticsearch_address

Bug #1673990 reported by Graeme Seaton
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Undecided
Graeme Seaton

Bug Description

Haproxy binds the elasticsearch service to kolla_internal_vip_address but the output templates for fluentd (td-agent) point to a non-existent kolla_external_vip_address.

Output should also be able to be sent to an external elasticsearch instance (as per the documentation regarding overriding elasticsearch_address)

The attached diff changes these settings so that fluentd outputs to either the default elasticsearch_address (i.e. kolla_internal_vip_address) or to the external elasticsearch instance.

Revision history for this message
Graeme Seaton (gseaton) wrote :
description: updated
summary: - fluentd output to elasticsearch should use internal vip address
+ fluentd output to elasticsearch should use elasticsearch_address
Revision history for this message
Graeme Seaton (gseaton) wrote :

Added to gerrit.

Graeme Seaton (gseaton)
Changed in kolla-ansible:
assignee: nobody → Graeme Seaton (gseaton)
Revision history for this message
Graeme Seaton (gseaton) wrote :

Fix committed in kolla-ansible https://review.openstack.org/#/c/447654/

Changed in kolla-ansible:
status: New → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

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

commit 7f3cab65f03f4a66ee26f8c415947c2bdec6fb11
Author: Graeme Seaton <email address hidden>
Date: Mon Mar 20 19:27:24 2017 +0000

    Set fluentd output to elasticsearch to use elasticsearch_address

    Haproxy binds the elasticsearch service to kolla_internal_vip_address but
    the output templates for fluentd (td-agent) point to a non-existent
    kolla_external_vip_address.

    Output should also be able to be sent to an external elasticsearch
    instance (as per the documentation regarding overriding
    elasticsearch_address)

    Change these settings so that fluentd outputs to either
    the default elasticsearch_address (i.e. kolla_internal_vip_address) or to
    the external elasticsearch instance.

    Closes-Bug: #1673990
    Change-Id: I081533ae8ea9aad186e9c44e1dee069729931453

Changed in kolla-ansible:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/457907

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

Reviewed: https://review.openstack.org/457907
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=e7b0e3e31819b29852338663714666a7a6e4d1c5
Submitter: Jenkins
Branch: stable/ocata

commit e7b0e3e31819b29852338663714666a7a6e4d1c5
Author: Graeme Seaton <email address hidden>
Date: Mon Mar 20 19:27:24 2017 +0000

    Set fluentd output to elasticsearch to use elasticsearch_address

    Haproxy binds the elasticsearch service to kolla_internal_vip_address but
    the output templates for fluentd (td-agent) point to a non-existent
    kolla_external_vip_address.

    Output should also be able to be sent to an external elasticsearch
    instance (as per the documentation regarding overriding
    elasticsearch_address)

    Change these settings so that fluentd outputs to either
    the default elasticsearch_address (i.e. kolla_internal_vip_address) or to
    the external elasticsearch instance.

    Closes-Bug: #1673990
    Change-Id: I081533ae8ea9aad186e9c44e1dee069729931453
    (cherry picked from commit 7f3cab65f03f4a66ee26f8c415947c2bdec6fb11)

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 5.0.0.0b2

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

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

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

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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