Information in vnf_package_vnfd DB is not Deleted while uploading is in progress

Bug #1894169 reported by LiangLu
This bug affects 1 person
Affects Status Importance Assigned to Milestone

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)

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)

LiangLu (lianglu)
Changed in tacker:
assignee: nobody → LiangLu (lianglu)
LiangLu (lianglu)
description: updated
Revision history for this message
LiangLu (lianglu) wrote :

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

If we are supposing to add other conflict status should we also make a report to etsi?

Yasufumi Ogawa (yasufum)
Changed in tacker:
importance: Undecided → High
Revision history for this message
Itsuro Oda (oda-g) wrote :

The description saids 'Typically'.
In 9.3.6 "Precondition: The individual VNF package resource has been created, the operational state of the VNF package is DISABLED, and the usage state of the VNF package is NOT_IN_USE. "
I think it is OK to return 409 Conflict when operational-state/usage-state is other than DISABLED/NOT_IN_USE.

Revision history for this message
Yasufumi Ogawa (yasufum) wrote :

Hi Liang,
Could I confirm the current status?

Revision history for this message
Ayumu Ueha (ueha) wrote :

Sorry for the late, Liang have been left from my company.
As Oda-san says, I think there is no problem with returning 409 when operational-state/usege-state other than DISABLE/NOT_IN_USE, so I think it needs to be fixed.

To: Ogawa-san
BTW, do you know if your colleagues at NTT have given any feedback to ETSI about this issue?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.