NetworkNotFound should be raised when a network is not found in network manager
Bug #872522 reported by
Nachi Ueno
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Unassigned | ||
OpenStack Quality Assurance |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
db.network_
In that case some method in network manager such as delete_network raises AttriuteError.
But this is not informative. In this case, Network manager should throw exception.
Following methods have same problem.
- FloatingIP.
- NetworkManager.
- NetworkManager.
- NetworkManager.
- NetworkManager.
- NetworkManager.
- NetworkManager.
- VlanManager.
Changed in nova: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in openstack-qa: | |
status: | New → In Progress |
Changed in nova: | |
assignee: | nobody → Nachi Ueno (nati-ueno) |
Changed in openstack-qa: | |
assignee: | nobody → Nachi Ueno (nati-ueno) |
importance: | Undecided → Medium |
Changed in nova: | |
assignee: | Nachi Ueno (nati-ueno) → nobody |
Changed in openstack-qa: | |
assignee: | Nachi Ueno (nati-ueno) → nobody |
Changed in openstack-qa: | |
status: | In Progress → Won't Fix |
To post a comment you must log in.
https:/ /github. com/ntt- pf-lab/ nova/tree/ openstack- qa-nova- 872522