Vnf package upload fails with incorrect http status code

[Tushar Patil]

If I delete an on-boarded vnf package and try to upload a vnf package using the same vnf package uuid, it fails with 409 error.

Actual Result: 409 error
Expected Result: 404 error

[Hiroo Kitamura (h-kitamura)]

Hi, I checked whether this bug occurred, but it seemed to have been already fixed.
Is it right?
If so, let's close this bug.

$ openstack vnf package list
+--------------------------------------+------------------+------------------+-------------+-------------------+
| Id | Vnf Product Name | Onboarding State | Usage State | Operational State |
+--------------------------------------+------------------+------------------+-------------+-------------------+
| 0e02ff7e-d180-4b18-861e-49220f6234ed | Sample VNF | ONBOARDED | NOT_IN_USE | DISABLED |
+--------------------------------------+------------------+------------------+-------------+-------------------+
$ openstack vnf package delete 0e02ff7e-d180-4b18-861e-49220f6234ed
All specified vnf-package(s) deleted successfully
$ openstack vnf package list

$ openstack vnf package upload --path ./sample_vnf_pkg.zip 0e02ff7e-d180-4b18-861e-49220f6234ed --debug
~~~~~~~~~~~~
REQ: curl -g -i -X PUT http://127.0.0.1:9890/vnfpkgm/v1/vnf_packages/0e02ff7e-d180-4b18-861e-49220f6234ed/package_content -H "Accept: application/zip" -H "Content-Type: application/zip" -H "User-Agent: python-tackerclient" -H "X-Auth-Token: {SHA256}3ffaa6c2af99747f35fbfdf62d31010b01eff5ae057a022b5ced9c004d66ab14" -d '<_io.BufferedReader name='./sample_vnf_pkg.zip'>'
Starting new HTTP connection (1): 127.0.0.1:9890
http://127.0.0.1:9890 "PUT /vnfpkgm/v1/vnf_packages/0e02ff7e-d180-4b18-861e-49220f6234ed/package_content HTTP/1.1" 404 118
RESP: [404] Connection: keep-alive Content-Length: 118 Content-Type: application/json; charset=UTF-8 Date: Thu, 14 May 2020 05:48:49 GMT X-Openstack-Request-Id: req-eb233b94-5343-4cc9-a4a8-0a3bce5afa75
RESP BODY: {"itemNotFound": {"code": 404, "message": "Can not find requested vnf package: 0e02ff7e-d180-4b18-861e-49220f6234ed"}}
PUT call to nfv-orchestration for http://127.0.0.1:9890/vnfpkgm/v1/vnf_packages/0e02ff7e-d180-4b18-861e-49220f6234ed/package_content used request id req-eb233b94-5343-4cc9-a4a8-0a3bce5afa75
Error message: {"itemNotFound": {"code": 404, "message": "Can not find requested vnf package: 0e02ff7e-d180-4b18-861e-49220f6234ed"}}
~~~~~~~~~~~~

[Tushar Patil (tpatil)]

Now, this issue is not reproducible.

[Hiroo Kitamura (h-kitamura)]

If so, is it OK to close this bug?

[Tushar Patil (tpatil)]

> If so, is it OK to close this bug?
Yes, you can close this bug.

[Yasufumi Ogawa (yasufum)]

Thanks Tushar and Hiroo. It's closed.