VNF should not be allowed to delete separately, if part of an active NS
Bug #1691363 reported by
dharmendra
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
Fix Released
|
High
|
yong sheng gong |
Bug Description
In the current code, anyone can delete a VNF even it is the part of an active NS.
This behavior should be fixed.
Changed in tacker: | |
assignee: | nobody → dharmendra (dharmendra-kushwaha) |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in tacker: | |
milestone: | none → queens-2 |
Changed in tacker: | |
milestone: | queens-2 → queens-3 |
Changed in tacker: | |
assignee: | dharmendra (dharmendra-kushwaha) → yong sheng gong (gongysh) |
To post a comment you must log in.
I also met this bug that when I deleted one VNF belong to an activate NS, the NS's vnf_ids didn't pop the deleted vnf's id. So I believed that should mark the vnf is part of the NS when created vnf during NS initializing.