Associating float IP failed when vpnaas and dvr is both enabled
Bug #1644146 reported by
Chao Guo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Expired
|
Undecided
|
Unassigned |
Bug Description
I using version 3.0.1 and official ubuntu-source images,and have both vpnaas and dvr enabled.
When associating float IP to Instance, it failed. Dashboard reported that it cannot find the l3 agent on compute node, and there is no any l3 agnet container running on compute node.
Changed in kolla: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in kolla: | |
milestone: | none → ocata-3 |
Changed in kolla: | |
milestone: | ocata-3 → ocata-rc1 |
Changed in kolla: | |
milestone: | ocata-rc1 → pike-1 |
Changed in kolla: | |
milestone: | pike-2 → pike-3 |
Changed in kolla: | |
milestone: | pike-3 → pike-rc1 |
Changed in kolla: | |
milestone: | pike-rc1 → queens-1 |
Changed in kolla: | |
milestone: | queens-2 → queens-3 |
Changed in kolla: | |
milestone: | queens-3 → queens-rc1 |
Changed in kolla: | |
milestone: | queens-rc1 → queens-rc2 |
Changed in kolla: | |
milestone: | queens-rc2 → rocky-1 |
Changed in kolla: | |
milestone: | rocky-2 → rocky-3 |
To post a comment you must log in.
vpnaas and dvr cannot work together, so it should be checked and reported during prechecks.