l2population configuration is inconsistent for different agents
Bug #1481138 reported by
Li Ma
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
I run devstack for dev. I noticed that l2population configuration is not consistent for lb-agent and ovs-agent.
For lb-agent, l2population is in the section [vxlan], while for ovs-agent, it is in the section [agent].
Moreover, the devstack is set this configuration in [agent] that causes lb-agent malfunction.
It is easy to fix it in the devstack, but, in a long run, I think it is better to deal with it for agent side. I think for both agents, the common configuration like l2population should be in the [agent] section.
| Changed in neutron: | |
| assignee: | nobody → Li Ma (nick-ma-z) |
Revision history for this message
| Li Ma (nick-ma-z) wrote | #1 |
| Changed in neutron: | |
| assignee: | Li Ma (nick-ma-z) → nobody |
| Changed in neutron: | |
| assignee: | nobody → Dongcan Ye (hellochosen) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on neutron (master) | #2 |
| Changed in neutron: | |
| assignee: | Dongcan Ye (hellochosen) → nobody |
Revision history for this message
| Lajos Katona (lajos-katona) wrote | #3 |
| Changed in neutron: | |
| status: | In Progress → Won't Fix |
To post a comment you must log in.
An rfe is proposed for this bug. https:/