Charm does not use the provider extra binding

Bug #1782433 reported by David Ames
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Neutron Dynamic Routing charm
Fix Released
Critical
David Ames

Bug Description

The charm has the extra-binding provider to ensure the router id is set to an IP on the provider network. However, the template is calling the speaker_ip which is only used when in a relation with anther charm (i.e. quagga).

In testing fixes for this it was also discovered the bgp_dragent.ini file is rendered with 640 root:root perms which stops neutron from reading the file.

David Ames (thedac)
Changed in charm-neutron-dynamic-routing:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → David Ames (thedac)
Changed in charm-neutron-dynamic-routing:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-neutron-dynamic-routing (master)

Reviewed: https://review.openstack.org/583704
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-dynamic-routing/commit/?id=ba7b42e36c1d527433852e3fbb93b64248b9f9b7
Submitter: Zuul
Branch: master

commit ba7b42e36c1d527433852e3fbb93b64248b9f9b7
Author: David Ames <email address hidden>
Date: Wed Jul 18 12:04:10 2018 -0700

    Use the provider network for router id

    The router id for the dragent must be on the provider network. The
    charm was using the BGP speaker_ip which is only used for related
    test services. (i.e. quagga).

    This change guarantees the router id uses the provider extra binding
    IP.

    It also sets the group ownership to neutron for rendered config files.

    Closes-Bug: #1782433
    Partial-Bug: #1782444
    Change-Id: I4761b4c5b80a398e13e4cdf880b773df489f53b9

Changed in charm-neutron-dynamic-routing:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-dynamic-routing (stable/18.05)

Fix proposed to branch: stable/18.05
Review: https://review.openstack.org/584483

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-neutron-dynamic-routing (stable/18.05)

Reviewed: https://review.openstack.org/584483
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-dynamic-routing/commit/?id=50014ed7147210ec89b8a9f29e1dd7c0c70b0b1d
Submitter: Zuul
Branch: stable/18.05

commit 50014ed7147210ec89b8a9f29e1dd7c0c70b0b1d
Author: David Ames <email address hidden>
Date: Wed Jul 18 12:04:10 2018 -0700

    Use the provider network for router id

    The router id for the dragent must be on the provider network. The
    charm was using the BGP speaker_ip which is only used for related
    test services. (i.e. quagga).

    This change guarantees the router id uses the provider extra binding
    IP.

    It also sets the group ownership to neutron for rendered config files.

    cherry picked from commit ba7b42e36c1d527433852e3fbb93b64248b9f9b7

    Closes-Bug: #1782433
    Partial-Bug: #1782444
    Change-Id: I4761b4c5b80a398e13e4cdf880b773df489f53b9

David Ames (thedac)
Changed in charm-neutron-dynamic-routing:
milestone: none → 19.04
David Ames (thedac)
Changed in charm-neutron-dynamic-routing:
status: Fix Committed → Fix Released
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.