"OperationParams" Type Mismatch in Individual VNF Operation Occurrence Compliance Test
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
New
|
Medium
|
renu rani |
Bug Description
[Issue]
Zuul job for compliance testing in Tacker is currently in a non-voting state. While addressing compliance test , "OperationParams" type mismatch issue is found in Individual VNF Operation Occurrence Compliance Test.
[Issue Detail]
Executed Individual VNF operation occurrence compliance test in Tacker.
<Testcase>
tacker.
<Encountered an error> 'operationParam' is not of type object.
<Error message>
<status status="FAIL" starttime="20230904 08:49:24.324" endtime="20230904 08:49:24.423" critical=
<Error location> https:/
[Cause]
In NFV-TST 010 “~/api-
The type of ‘operationParams’ was validated in the Tacker code side, and it was observed that 'operationParams' is of type string.
<Cause code>
Validation check in ~/apitests/
'operationParams' is defined as of type 'string' . https:/
[Proposal]
Tacker side code need to be fixed in file ~/tacker/
<Impact of approach>
Below LCM operations are directly impacted while changing operation_param data type from string to object.
•Instantiate
def _instantiate : https:/
•Terminate
def _terminate :
https:/
•Heal
def _heal:
https:/
•Cancel
def cancel:
https:/
•Fail
def _fail:
https:/
•change external connectivity
def _change_ext_conn:
https:/
<Impact on db>
Table vnf_lcm_op_occs will be impacted as currently data type of operation_params is longtext.
description: | updated |
Changed in tacker: | |
assignee: | nobody → renu rani (renur) |
description: | updated |
description: | updated |
Changed in tacker: | |
importance: | Undecided → Medium |