Compliance test fails due to schema definition error in TST 2.6.1 repository

Bug #2060430 reported by Shivam Shukla
6
This bug affects 1 person
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 ("virtualLinkDescId") and Tacker's API response schema ("vnfVirtualLinkDescId").

[Issue Detail]

Executed Individual VNF operation occurrence compliance test in Tacker.

<Testcase>
tacker.tests.compliance.sol003.test_vnflcm.IndividualVnfLcmOperationOccurenceTest.test_get_ind_vnf_lcm_op_occs

<Encountered an error> 'vnfVirtualLinkDescId' is a required property.

[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.schema.json file includes "virtualLinkDescId" as a field name. Conversely, in the Tacker VNFLCM API response schema, the corresponding field name is "vnfVirtualLinkDescId".

According to the ETSI specification document, the correct field name should be "vnfVirtualLinkDescId". Therefore, the issue lies with NFV-TST where "virtualLinkDescId" is defined in the VnfLcmOpOcc schema instead of "vnfVirtualLinkDescId". Due to this, test is getting failed.

<VnfLcmOpOcc schema>
https://forge.etsi.org/rep/nfv/api-tests/-/blob/2.6.1-fix-plu/SOL003/VNFLifecycleManagement-API/schemas/VnfLcmOpOcc.schema.json

<ETSI specification document>
https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf

<Tacker Vnflcm API response schema>
https://github.com/openstack/tacker/blob/master/api-ref/source/v1/samples/vnflcm/show-vnflcm-operation-occurrence-response.json

[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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.