Failed to operate legacy cnf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
Fix Released
|
Medium
|
Ayumu Ueha |
Bug Description
When I performed cnf operation (legacy) according to the procedure described in the document [1], the following error occurred.
1. vnf create error caused by policies parameter
2. vnf scale error due to key error of policy[]
3. no retry interval during vnf delete wait
[1. vnf create error caused by policies parameter]
=======
When vnf create operation, the following error occurred.
$ openstack vnf descriptor create --vnfd-file tosca-vnfd-
tosca-parser failed: -
The pre-parsed input failed validation with the following error(s):
This error is due to a change that now causes tosca-parser to check the required parameter of policies [2].
To avoid the above error, I added the required parameter to VNFD policies and re-executed create, but the following error occurred.
$ openstack vnf create --vnfd-name VNFD1 --vim-name vim-kubernetes VNF1
Found unsupported keys for ['default_
To avoid this "Found unsupported keys" error, it is necessary to remove the checking for unsupported keys of policies [3].
[2. vnf scale error due to key error of policy[]]
=======
After I fixed above create error, It failed to scale vnf because of following error.
$ openstack vnf scale --scaling-
Request Failed: internal server error while processing your request.
[req-1ef50574-
Traceback (most recent call last):
File "/opt/stack/
result = method(
File "/opt/stack/
obj = obj_creator(
File "/opt/stack/
self.
File "/opt/stack/
last_event_id = _vnf_policy_
File "/opt/stack/
_handle_
File "/usr/local/
self.
File "/usr/local/
six.
File "/usr/local/
raise value
File "/opt/stack/
region_
File "/opt/stack/
return getattr(driver, method_
File "/opt/stack/
return method(*args, **kwargs)
File "/opt/stack/
context, policy[
KeyError: 'vnf_instance_id'
`policy[
But in legacy route, `vnf_instance_id` is not added to `policy[]`, so this error is occurred.
The current implementation determines legacy or sol based on the existence of vnf_resource.
To avoid this error, it is necessary to change the legacy or sol decision, and I think it's best to use `policy ['vnf_instance_
[3. no retry interval during vnf delete wait]
=======
I found a problem that the wait process ends immediately, because there is no interval of wait retry process [5].
If the deletion finishes immediately, there is no problem, but if it takes time, an error will occur.
Reference
======
[1] https:/
[2] https:/
[3] https:/
[4] https:/
[5] https:/
Changed in tacker: | |
assignee: | nobody → Ayumu Ueha (ueha) |
Changed in tacker: | |
importance: | Undecided → Medium |
Changed in tacker: | |
status: | In Progress → Fix Released |
Fix proposed to branch: master /review. opendev. org/c/openstack /tacker/ +/783626
Review: https:/