NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2022-12-06T15:41:22Zhttps://forge.etsi.org/rep/nfv/SOL012/-/issues/3Query params should not be defined as global parameters in SOL012_params.yaml.2022-12-06T15:41:22ZVlademir BrusseQuery params should not be defined as global parameters in SOL012_params.yaml.SOL012 is using the same parameters in the file SOL012_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the u...SOL012 is using the same parameters in the file SOL012_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL012_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL011/-/issues/3Query params should not be defined as global parameters in SOL011_params.2022-12-06T16:58:30ZVlademir BrusseQuery params should not be defined as global parameters in SOL011_params.SOL011 is using the same parameters in the file SOL011_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the u...SOL011 is using the same parameters in the file SOL011_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL011_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL009/-/issues/4Query params should not be defined as global parameters in SOL009_params.yaml.2022-01-19T11:54:19ZVlademir BrusseQuery params should not be defined as global parameters in SOL009_params.yaml.SOL009 is using the same parameters in the file SOL009_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the u...SOL009 is using the same parameters in the file SOL009_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL009_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL002-SOL003/-/issues/3Query params should not be defined as global parameters in SOL002SOL003_param...2022-01-25T10:10:17ZVlademir BrusseQuery params should not be defined as global parameters in SOL002SOL003_params.yaml.SOL002 and SOL003 are using the same parameters in the file SOL002SOL003_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open po...SOL002 and SOL003 are using the same parameters in the file SOL002SOL003_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL002SOL003_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/21Query params should not be defined as global parameters in SOL005_params.yaml2022-01-31T08:24:12ZVlademir BrusseQuery params should not be defined as global parameters in SOL005_params.yamlSOL005 is using the same parameters in the file SOL005_params.yaml of the GET methods for all interfaces including "NS Lifecycle Management" and "NS Performance Management" interfaces, for example, but the parameters for both are differe...SOL005 is using the same parameters in the file SOL005_params.yaml of the GET methods for all interfaces including "NS Lifecycle Management" and "NS Performance Management" interfaces, for example, but the parameters for both are different and can be different for others.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL005_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL009/-/issues/3OpenAPI wiki page - NFVManoConfigurationAndInformationManagement-API of v3.5....2022-01-31T11:10:58ZVlademir BrusseOpenAPI wiki page - NFVManoConfigurationAndInformationManagement-API of v3.5.1 showing several errors on "Editor" page.In the "NFVManoConfigurationAndInformationManagement-API" of SOL009 v3.5.1 it is showing several errors when rendering the swagger "Editor" page on Chrome browser.
The use of "oneOf" should be investigated here since in v3.3.1 does not ...In the "NFVManoConfigurationAndInformationManagement-API" of SOL009 v3.5.1 it is showing several errors when rendering the swagger "Editor" page on Chrome browser.
The use of "oneOf" should be investigated here since in v3.3.1 does not have this issue. If so, we need a solution for that.
Structural error at paths./peer_entities.post.requestBody
should have required property '$ref'
missingProperty: $ref
Jump to line 18171
Structural error at paths./peer_entities.post.requestBody
should match exactly one schema in oneOf
Jump to line 18171
...
Giacomo answered that "this is because some data types inside this API have "type" as attribute names, which is also an OpenAPI keyword. So it is a kind of warning that the editor page tool gives to signal it. Not sure how to be avoided to be honest, as we cannot change the attribute name "type" otherwise it will not be compliant with SOL specs."Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL012/-/issues/2OpenAPI wiki page - "models" session in "UI" links and "schemas" session in "...2022-12-06T15:41:22ZVlademir BrusseOpenAPI wiki page - "models" session in "UI" links and "schemas" session in "Editor" links.Same issue in SOL012 v3.4.1 as reported for SOL009 and SOL011.
All APIs in the OpenAPIs wiki page have:
- UI links – there is a “models” section in OpenAPIs swagger UI pages, this section does not exist in other APIs
- Editor link...Same issue in SOL012 v3.4.1 as reported for SOL009 and SOL011.
All APIs in the OpenAPIs wiki page have:
- UI links – there is a “models” section in OpenAPIs swagger UI pages, this section does not exist in other APIs
- Editor links – there is a “schemas” section in OpenAPIS swagger Editor pages, this section does not exist in other APIs
As these sections are not showed in other APIs there is a need to make them as a standard, the sections need to be removed in SOL012 or included in the other APIs.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL011/-/issues/2OpenAPI wiki page - "models" session in "UI" links and "schemas" session in "...2022-12-06T16:58:30ZVlademir BrusseOpenAPI wiki page - "models" session in "UI" links and "schemas" session in "Editor" links.The APIs "SOL011-NSLifecycleOperationGranting-API" and "SOL011-NSInstanceUsageNotification-API" in the OpenAPIs wiki page have:
- UI links – there is a “models” section in OpenAPIs swagger UI pages, this section does not exist in othe...The APIs "SOL011-NSLifecycleOperationGranting-API" and "SOL011-NSInstanceUsageNotification-API" in the OpenAPIs wiki page have:
- UI links – there is a “models” section in OpenAPIs swagger UI pages, this section does not exist in other APIs
- Editor links – there is a “schemas” section in OpenAPIS swagger Editor pages, this section does not exist in other APIs
As these sections are not showed in other APIs there is a need to make them as a standard, the sections need to be removed in SOL011 or included in the other APIs.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL009/-/issues/2OpenAPI wiki page - "models" session in "UI" links and "schemas" session in "...2022-05-28T07:54:10ZVlademir BrusseOpenAPI wiki page - "models" session in "UI" links and "schemas" session in "Editor" links.All APIs in the OpenAPIs wiki page have:
- UI links – there is a “models” section in OpenAPIs swagger UI pages, this section does not exist in other APIs
- Editor links – there is a “schemas” section in OpenAPIS swagger Editor pages,...All APIs in the OpenAPIs wiki page have:
- UI links – there is a “models” section in OpenAPIs swagger UI pages, this section does not exist in other APIs
- Editor links – there is a “schemas” section in OpenAPIS swagger Editor pages, this section does not exist in other APIs
These issues were reported before, I think in v3.3.1, as these sections are not showed in other APIs there is a need to make them as a standard, the sections need to be removed in SOL009 or included in the other APIs.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/api-tests/-/issues/190Wrong Problem Details JSON Object set in Keywords Check HTTP Response Body Js...2021-10-05T10:15:18ZyaoyuyWrong Problem Details JSON Object set in Keywords Check HTTP Response Body Json Schema Is ProblemDetails SOL005 VNFPackageManagementAPI v2.6.1When check HTTP Response Body Json Schema Is ProblemDetails
the problem details json object should be application/problem+json according to the RFC7807
but now the value is application/json
https://datatracker.ietf.org/doc/html/rfc7807When check HTTP Response Body Json Schema Is ProblemDetails
the problem details json object should be application/problem+json according to the RFC7807
but now the value is application/json
https://datatracker.ietf.org/doc/html/rfc7807https://forge.etsi.org/rep/nfv/api-tests/-/issues/187Missing set suite variable in keyword in vnfpackagemanagement keyword at mult...2021-09-21T16:43:57ZsinghadiMissing set suite variable in keyword in vnfpackagemanagement keyword at multiple check position```
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
GET ${apiRoot}/${apiName}/${apiVersion}/vnf_packages/${vnfPkgZipVNFD}/vnfd
Check HTTP Response Status Code Is ...```
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
GET ${apiRoot}/${apiName}/${apiVersion}/vnf_packages/${vnfPkgZipVNFD}/vnfd
Check HTTP Response Status Code Is 200
```https://forge.etsi.org/rep/nfv/api-tests/-/issues/186Unsupported function tested in test case VNFLifecycleManagementAPI Subscripti...2021-06-28T13:36:44ZyaoyuyUnsupported function tested in test case VNFLifecycleManagementAPI Subscriptions SOL003 v2.6.1According to the specicfication file, the parameters supported by the GET method on subscriptions are filter and nextpage_opaque_marker.<br>
However, the attribute selector like exclude_fileds,exlude_default is also tested in Subscriptio...According to the specicfication file, the parameters supported by the GET method on subscriptions are filter and nextpage_opaque_marker.<br>
However, the attribute selector like exclude_fileds,exlude_default is also tested in Subscriptions tests.<br>
Test cases are GET subscriptions with all_fields attribute selector, GET subscriptions with exclude_default attribute selector,GET subscriptions with fields attribute selector,GET subscriptions with exclude_fields attribute selector.
Is this part missing in the specification file or the test cases should be removed?
https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf (Table 5.4.18.3.2-1: URI query parameters supported by the GET method on this resource)https://forge.etsi.org/rep/nfv/api-tests/-/issues/184SOL003 and SOL002 /vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId}} ...2021-03-18T16:21:01ZguptanavSOL003 and SOL002 /vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId}} API V2.6.1 for DELETE methodWhen testing case '**DELETE an individual subscriptio**n' it return 204 but expected is 405
*Attached are complete logs of the same* :
[f97f0fb8-e205-4809-b9d5-1d63397702c4.VNFLifecycleManagement-API.IndividualSubscription.log.html](/...When testing case '**DELETE an individual subscriptio**n' it return 204 but expected is 405
*Attached are complete logs of the same* :
[f97f0fb8-e205-4809-b9d5-1d63397702c4.VNFLifecycleManagement-API.IndividualSubscription.log.html](/uploads/0e005e4244c617063e75e8f0c99d00ee/f97f0fb8-e205-4809-b9d5-1d63397702c4.VNFLifecycleManagement-API.IndividualSubscription.log.html)
[2051f687-d3e2-42d0-af2d-502e083b3e5d.VNFLifecycleManagement-API.IndividualSubscription.log.html](/uploads/da3801ebc4b4c25b68459ce48148815c/2051f687-d3e2-42d0-af2d-502e083b3e5d.VNFLifecycleManagement-API.IndividualSubscription.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/183SOL002/vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId}} API V2.4.1 ...2021-05-28T07:10:56ZguptanavSOL002/vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId}} API V2.4.1 GET methodWhen testing case '**GET Individual Subscription**' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[f97f...When testing case '**GET Individual Subscription**' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[f97f0fb8-e205-4809-b9d5-1d63397702c4.VNFLifecycleManagement-API.IndividualSubscription.log.html](/uploads/0f3e6f190ee24cf912e1830c827d6ef5/f97f0fb8-e205-4809-b9d5-1d63397702c4.VNFLifecycleManagement-API.IndividualSubscription.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/182SOL003/vnflcm/{apiMajorVersion}/subscriptions API V2.4.1 GET method2021-05-28T07:12:07ZguptanavSOL003/vnflcm/{apiMajorVersion}/subscriptions API V2.4.1 GET methodWhen testing case '**GET Subscriptions**' it got failed with
ValidationError: Validation error for schema Subscriptions.schema.json: ['VnfLcmOperationOccurrenceNotification', 'VnfIdentifierCreationNotification', 'VnfIdentifierDeletionN...When testing case '**GET Subscriptions**' it got failed with
ValidationError: Validation error for schema Subscriptions.schema.json: ['VnfLcmOperationOccurrenceNotification', 'VnfIdentifierCreationNotification', 'VnfIdentifierDeletionNotification'] is not of type 'string'
*Attached are complete logs of the same* :
[eef8526a-2352-4e1a-92bc-b2d5b0ef6d0a.VNFLifecycleManagement-API.Subscriptions.log.html](/uploads/23aba39ffede1974c3ea60b0e6897311/eef8526a-2352-4e1a-92bc-b2d5b0ef6d0a.VNFLifecycleManagement-API.Subscriptions.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/181SOL002/vnflcm/{apiMajorVersion}/subscriptions API V2.4.1 POST and GET method2021-05-28T07:12:01ZguptanavSOL002/vnflcm/{apiMajorVersion}/subscriptions API V2.4.1 POST and GET methodWhen testing case
* '**POST Create a new subscription**' it got failed with error message KeyError: '\n "filter"'
* '**GET Subscription**s' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: ...When testing case
* '**POST Create a new subscription**' it got failed with error message KeyError: '\n "filter"'
* '**GET Subscription**s' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[c2d987d0-fa4e-4736-8a54-39da4b21ae11.VNFLifecycleManagement-API.Subscriptions.log.html](/uploads/e9da042e5797c9be8c6eb6b169eac337/c2d987d0-fa4e-4736-8a54-39da4b21ae11.VNFLifecycleManagement-API.Subscriptions.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/180SOL003 and SOL002 /vnf_lcm_op_occs/${vnfLcmOpOccId}/failAPI V2.4.1 POST method2021-05-28T07:12:17ZguptanavSOL003 and SOL002 /vnf_lcm_op_occs/${vnfLcmOpOccId}/failAPI V2.4.1 POST methodWhen testing case '**POST Fail operation task**' some Internal Server Error and Can not find requested vnf instance
*Attached are complete logs of the same* :
[83880b26-4b18-4afd-ac97-f42efc8664d8.VNFLifecycleManagement-API.FailOperati...When testing case '**POST Fail operation task**' some Internal Server Error and Can not find requested vnf instance
*Attached are complete logs of the same* :
[83880b26-4b18-4afd-ac97-f42efc8664d8.VNFLifecycleManagement-API.FailOperationTask.log.html](/uploads/cad498e8efb7d12e3fe26bd938e9a292/83880b26-4b18-4afd-ac97-f42efc8664d8.VNFLifecycleManagement-API.FailOperationTask.log.html)
[733392c2-93bb-45ca-83ab-e7741c62022c.VNFLifecycleManagement-API.FailOperationTask.log.html](/uploads/e8dd8fd9cb1e39443bb3a0122aef4304/733392c2-93bb-45ca-83ab-e7741c62022c.VNFLifecycleManagement-API.FailOperationTask.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/179SOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId} API V2.4.1 ...2021-05-28T07:11:55ZguptanavSOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId} API V2.4.1 GET methodWhen testing case '**Get information about multiple VNF instances**' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of ...When testing case '**Get information about multiple VNF instances**' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[f67f0af5-65d2-4106-8fa8-8098ce53ef4c.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html](/uploads/41a8c1b4725743830389cc3852d5c57e/f67f0af5-65d2-4106-8fa8-8098ce53ef4c.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/178SOL003/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId} API V2.4.1 ...2021-03-17T10:27:38ZguptanavSOL003/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId} API V2.4.1 GET methodWhen testing case '**Get information about multiple VNF instances**' it got failed with error message 'resourse was not found.' comes. API path is wrong.${vnfLcmOpOccId} is missing.
*Attached are complete logs of the same* :
[b5d0cdb9...When testing case '**Get information about multiple VNF instances**' it got failed with error message 'resourse was not found.' comes. API path is wrong.${vnfLcmOpOccId} is missing.
*Attached are complete logs of the same* :
[b5d0cdb9-28bc-4dec-bf46-f27351c7c776.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html](/uploads/430e11132a7e71632366e486303d2ba5/b5d0cdb9-28bc-4dec-bf46-f27351c7c776.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/177SOL003/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId} API V2.4.1 ...2021-05-28T07:11:49ZguptanavSOL003/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId} API V2.4.1 GET methodWhen testing case '**Get information about multiple VNF instances**' it got failed with error message 'resourse was not found.' comes. API path is wrong.${vnfLcmOpOccId} is missing.
*Attached are complete logs of the same* :
[b5d0cdb9-...When testing case '**Get information about multiple VNF instances**' it got failed with error message 'resourse was not found.' comes. API path is wrong.${vnfLcmOpOccId} is missing.
*Attached are complete logs of the same* :
[b5d0cdb9-28bc-4dec-bf46-f27351c7c776.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html](/uploads/c9f63183b407c8dbcc692f1f007f943d/b5d0cdb9-28bc-4dec-bf46-f27351c7c776.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html)