neutron is setting ip_nonlocal_bind to 0 when enabled l3 ha
Bug #1698745 reported by
Jeffrey Zhang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
Invalid
|
High
|
Jeffrey Zhang | ||
Bug Description
Neutron is setting ip_nonlocal_bind to 0 when enabled l3 ha[0][1], whereas haproxy require ip_nonlocal_bind to 1.
If neutron-l3-agent is started before haproxy, haproxy container will never up.
[0] https:/
[1] https:/
Revision history for this message
| Jeffrey Zhang (jeffrey4l) wrote | #1 |
| Changed in kolla-ansible: | |
| importance: | Undecided → High |
| milestone: | none → pike-3 |
| assignee: | nobody → Jeffrey Zhang (jeffrey4l) |
| Changed in kolla-ansible: | |
| milestone: | pike-3 → pike-rc1 |
Revision history for this message
| Jeffrey Zhang (jeffrey4l) wrote | #2 |
| Changed in kolla-ansible: | |
| status: | New → Invalid |
To post a comment you must log in.
one possible solution is: set ip_nonlocal_bind to 1 in haproxy starting script.