The fip namespace can be destroyed on L3 agent restart
Bug #1383571 reported by
Carl Baldwin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
The scenario is described in a recent patch review [1]. The patch did not introduce the problem but it was noticed during review of the patch.
[1] https:/
| Changed in neutron: | |
| importance: | Undecided → Medium |
| tags: | added: l3-dvr-backlog |
| Changed in neutron: | |
| assignee: | nobody → Carl Baldwin (carl-baldwin) |
| status: | New → Confirmed |
| Changed in neutron: | |
| assignee: | Carl Baldwin (carl-baldwin) → nobody |
Revision history for this message
| Ryan Moats (rmoats) wrote | #1 |
| Changed in neutron: | |
| status: | Confirmed → Incomplete |
| status: | Incomplete → Invalid |
To post a comment you must log in.
I don't believe this is real, based on the following test:
deploy a three node setup (controller+
setup external net----
ping from instance to 8.8.8.8
restart l3 agent on network node multiple times - pings don't show a break
Based on the above, this can be marked invalid