Namespace handling is missing in vArmour's FWaaS agent and driver
Bug #1222968 reported by
Gary Duan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Invalid
|
Medium
|
Gary Duan | ||
Bug Description
When a neutron router is created when running vArmour's l3 agent, namespace was not handled.
Corresponding virtual router (VR) should be created and destroyed if namespace is enabled.
| tags: | added: fwaas |
| Changed in neutron: | |
| assignee: | nobody → Gary Duan (gduan) |
| status: | New → In Progress |
| Changed in neutron: | |
| importance: | Undecided → Medium |
| milestone: | none → havana-rc1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to neutron (master) | #1 |
| tags: | added: havana-rc-potential |
| Changed in neutron: | |
| milestone: | havana-rc1 → none |
| tags: |
added: havana-backport-potential removed: havana-rc-potential |
| Changed in neutron: | |
| status: | In Progress → Invalid |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/