Compliance test fails due to schema definition error in TST 2.6.1 repository
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
New
|
Undecided
|
Shivam Shukla |
Bug Description
[Issue]
Schema validation error occurs during Tacker compliance tests due to a discrepancy between NFV-TST's version 2.6.1 schema field ("virtualLinkDe
[Issue Detail]
Executed Individual VNF operation occurrence compliance test in Tacker.
<Testcase>
tacker.
<Encountered an error> 'vnfVirtualLink
[Cause]
Tacker currently offers support for NFV-TST version 2.6.1. During the execution of the Tacker compliance test, the schema of the API response is validated. It has been noted that certain test cases encounter compatibility issues between the defined schema and the schema of the API response returned by Tacker.
According to the analysis, in NFV-TST version 2.6.1-fix-plu, the VnfLcmOpOcc.
According to the ETSI specification document, the correct field name should be "vnfVirtualLink
<VnfLcmOpOcc schema>
https:/
<ETSI specification document>
https:/
<Tacker Vnflcm API response schema>
https:/
[Proposal]
Fix the issue on NFV-TST version 2.6.1 side by correcting the schema parameter.
Fix the issue on Tacker side by upgrading the NFV-TST version from 2.6.1-fix-plu to 2.8.1-fix-plu or higher which is used by tacker for testing.
Changed in tacker: | |
assignee: | nobody → Shivam Shukla (shivam-shukla3) |
description: | updated |
description: | updated |