openstack vnf package upload shows unexpected message
Bug #1847726 reported by
Tushar Patil
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-tackerclient |
Fix Released
|
Low
|
Manpreet Kaur |
Bug Description
$ openstack vnf package show dummy-id
Can not find requested vnf package: dummy-id
$openstack vnf package upload --path sample_vnf_pkg.zip dummy-id
404-tackerFault
In case of upload as well, user should see same error message as shown in case of "openstack vnf package show" command i.e. "Can not find requested vnf package: dummy-id".
Changed in python-tackerclient: | |
assignee: | nobody → Shubham Potale (shubhamp) |
Changed in python-tackerclient: | |
importance: | Undecided → Low |
Changed in python-tackerclient: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Originally this bug was fixed in the Ussuri release [1].
But in Victoria release, the error handling of non-existing VNF package problem+ json" and the reason for a failure
was modified, please refer to [2].
Now on passing non-existing vnf package uuid to "vnf package upload"
command, the tacker server sends an HTTP response with "Content-Type"
header as "application/
described in the JSON problem details object.
In the current design, tackerclient does not support content-type problem+ json", therefore the issue resurfaces.
"application/
Note: This bug should backport in the Victoria release.
[1] https:/ /review. opendev. org/c/openstack /python- tackerclient/ +/688886 /review. opendev. org/c/openstack /tacker/ +/747678/ 37/tacker/ api/vnfpkgm/ v1/controller. py
[2] https:/