Make nova.virt.firewall use the current network model
Bug #1112657 reported by
Amir Sadoughi
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Invalid
|
Undecided
|
Amir Sadoughi | ||
Bug Description
Related to bug 1044383, nova.virt.firewall needs to use the current nova.network.model instead of being dependent on legacy().
| Changed in nova: | |
| status: | New → Confirmed |
| Changed in nova: | |
| assignee: | nobody → Amir Sadoughi (amir-sadoughi) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
| Changed in nova: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Joe Gordon (jogo) wrote | #2 |
| Changed in nova: | |
| status: | In Progress → Incomplete |
| Changed in nova: | |
| status: | Incomplete → Invalid |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/