Information in vnf_package_vnfd DB is not Deleted while uploading is in progress
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tacker |
New
|
High
|
LiangLu | ||
Bug Description
We found if we run vnf delete package command soon after upload command,
delete command will return success however in vnf_package_vnfd database the vnf package seems not deleted.
Steps to reproduce:
1. run openstack vnf package upload
2. run openstack vnf package delete soon after upload command
3. use sql command to check vnf_packages table with uuid, the package is deleted (deleted=1)
4. use sql command to check vnf_package_vnfd with uuid, vnfd is not delete (deleted=0)
Reason:
we are assuming this bug may caused by delete and upload command is running simultaneously,
thus delete command finished while upload is in progress, something will be remained if
it's upload process started after delete command is finished.
Thus, to add a delete lock for vnf_packages with PROCESSING or ONBOARDING state might be
a solotion to this bug.
(now the delete lock is only enabled for ENABLED and IN_USE vnf packages)
| Changed in tacker: | |
| assignee: | nobody → LiangLu (lianglu) |
| description: | updated |
| LiangLu (lianglu) wrote | #1 |
| Changed in tacker: | |
| importance: | Undecided → High |
| Itsuro Oda (oda-g) wrote | #2 |
| Yasufumi Ogawa (yasufum) wrote | #3 |
| Ayumu Ueha (ueha) wrote | #4 |
Also, accroading to SOL 005, delete confilt is defined when vnf package is in ENABLED or IN_USE status:
Error: The operation cannot be executed currently,
due to a conflict with the state of the resource.
Typically, this is due to the fact that the operational
state of the VNF package resource is ENABLED or
there are running VNF instances which are
instantiated based on the concerned VNF package
(https:/
If we are supposing to add other conflict status should we also make a report to etsi?