Haproxy-in-namespace can't access external world
Bug #1342073 reported by
Sergey Vasilenko
This bug report is a duplicate of:
Bug #1340968: [library] network namespaces require net.ipv4.ip_forward.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Sergey Vasilenko |
Bug Description
Haproxy in namespace can't access to the external world if net.ipv4.ip_forward == 0 in host system.
Changed in fuel: | |
assignee: | nobody → Sergey Vasilenko (xenolog) |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 5.1 |
summary: |
- Haproxy-in-namespace can't access to the external world + Haproxy-in-namespace can't access external world |
Changed in fuel: | |
assignee: | Sergey Vasilenko (xenolog) → Sergii Golovatiuk (sgolovatiuk) |
Changed in fuel: | |
assignee: | Sergii Golovatiuk (sgolovatiuk) → Sergey Vasilenko (xenolog) |
To post a comment you must log in.
Solution:
VIP-in-namespace OCF script should monitor net.ipv4.ip_forward sysctl and setup it to '1' if need.