Charm does not use the provider extra binding
Bug #1782433 reported by
David Ames
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.
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 |
Changed in charm-neutron-dynamic-routing: | |
milestone: | none → 19.04 |
Changed in charm-neutron-dynamic-routing: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/583704 /git.openstack. org/cgit/ openstack/ charm-neutron- dynamic- routing/ commit/ ?id=ba7b42e36c1 d527433852e3fbb 93b64248b9f9b7
Committed: https:/
Submitter: Zuul
Branch: master
commit ba7b42e36c1d527 433852e3fbb93b6 4248b9f9b7
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 8e13e4cdf880b77 3df489f53b9
Partial-Bug: #1782444
Change-Id: I4761b4c5b80a39