NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2021-06-03T08:49:17Zhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/165Using the same parameter when checking full size and Content-length SOL003 v2...2021-06-03T08:49:17ZyaoyuyUsing the same parameter when checking full size and Content-length SOL003 v2.6.1 VNFPackageManagementAPISame parameter is used to check for the file size and range size.and they can only be eqaul if the range size is same with the file size.
eg. the file size is 51 and the request range is range :bytes=0-50
so the response in Content-R...Same parameter is used to check for the file size and range size.and they can only be eqaul if the range size is same with the file size.
eg. the file size is 51 and the request range is range :bytes=0-50
so the response in Content-Range will be bytes 0-50/51
and the Content-Length will be 51 too
Another situation is the file size is 1000 and the request range is range :bytes=0-50
so the response in Content-Range will be bytes 0-50/1000
and the Content-Length will be 51
The parameter used to be ${full_size} and ${length} but it is changed now.
```
Check HTTP Response Header Content-Range Is Present and Matches the requested range
Log Check Content-Range HTTP Header
Should Contain ${response['headers']} Content-Range
Should Be Equal As Strings ${response['headers']['Content-Range']} bytes ${range}/${full_length}
Log Header Content-Range is present
Check HTTP Response Header Content-Length Is Present and Matches the requested range length
Log Check Content-Length HTTP Header
Should Contain ${response['headers']} Content-Length
Should Be Equal As Integers ${response['headers']['Content-Length']} ${full_length}
Log Header Content-Length is present
```https://forge.etsi.org/rep/nfv/api-tests/-/issues/164SOL005 NSDManagement-API Subscriptions NFVO_DUPLICATION==0 is used in both te...2021-02-23T19:05:20ZvignaudSOL005 NSDManagement-API Subscriptions NFVO_DUPLICATION==0 is used in both test cases.In both use case :
`Create duplicated NSD Management subscription with NFVO not creating duplicated subscriptions`
and
`Create duplicated NSD Management subscription with NFVO creating duplicated subscriptions`
Seems to use NFVO_DU...In both use case :
`Create duplicated NSD Management subscription with NFVO not creating duplicated subscriptions`
and
`Create duplicated NSD Management subscription with NFVO creating duplicated subscriptions`
Seems to use NFVO_DUPLICATION==0 for skipping the test.https://forge.etsi.org/rep/nfv/api-tests/-/issues/163SOL005 NSDManagement IndividualSubscription PUT & PATCH methods fail to evalu...2021-03-04T08:26:19ZvignaudSOL005 NSDManagement IndividualSubscription PUT & PATCH methods fail to evaluate JsonThose methods fail with error message :
`Evaluating expression 'json.loads('''{'id': '527bb09d-29e2-4025-962e-1e21134a6836', <...SNIP...>''')' failed: JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 2 ...Those methods fail with error message :
`Evaluating expression 'json.loads('''{'id': '527bb09d-29e2-4025-962e-1e21134a6836', <...SNIP...>''')' failed: JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 2 (char 1)`
[log.html](/uploads/38b97df5a0ca96e185e8c0d123fc86bf/log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/162SOL005 IndividualNSDescriptor nsdUsageState is retreived on a 4042021-06-03T08:49:17ZvignaudSOL005 IndividualNSDescriptor nsdUsageState is retreived on a 404In `GET Individual Network Service Descriptor Information with invalid resource identifier` test case fail because
`Resolving variable '${response['body']['nsdUsageState']}' failed: KeyError: 'nsdUsageState'`
Of course it does not exi...In `GET Individual Network Service Descriptor Information with invalid resource identifier` test case fail because
`Resolving variable '${response['body']['nsdUsageState']}' failed: KeyError: 'nsdUsageState'`
Of course it does not exist on a ProblemDetails response.
[log.html](/uploads/4085f817643c1c793a5cc186e5a6389f/log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/161SOL002 / IndividualVnfLcmOperationOccurence / 2.6.1 Multiple problems with PA...2021-06-03T08:49:17ZvignaudSOL002 / IndividualVnfLcmOperationOccurence / 2.6.1 Multiple problems with PATCH methodsHi,
According SOL002 v2.6.1 §5.4.3.3.4 The method PATCH exists.
Note that the patch method is using a vnfLcmOpOccId
> Patch ${apiRoot}/${apiName}/${apiVersion}/vnf_instances/${vnfLcmOpOccId}
According SOL002 v2.6.1 §5.4.3.3.5 The metho...Hi,
According SOL002 v2.6.1 §5.4.3.3.4 The method PATCH exists.
Note that the patch method is using a vnfLcmOpOccId
> Patch ${apiRoot}/${apiName}/${apiVersion}/vnf_instances/${vnfLcmOpOccId}
According SOL002 v2.6.1 §5.4.3.3.5 The method DELETE exists.
And same strange Id
> Delete ${apiRoot}/${apiName}/${apiVersion}/vnf_instances/${vnfLcmOpOccId}https://forge.etsi.org/rep/nfv/api-tests/-/issues/160SOL002/VNFLifecycleManagement/IndividualVNFInstance/2.6.1 DELETE queries with...2021-09-20T10:03:29ZvignaudSOL002/VNFLifecycleManagement/IndividualVNFInstance/2.6.1 DELETE queries with Content-Type: application/merge-patch+jsonHi,
When running the complete test IndividualVNFInstance.robot the 2 latest queries are DELETE one. And both are called with the header of a PATCH :
![image](/uploads/9cd1e5a24af0e54342cac66ac669331c/image.png) [log.html](/uploads/b527cf...Hi,
When running the complete test IndividualVNFInstance.robot the 2 latest queries are DELETE one. And both are called with the header of a PATCH :
![image](/uploads/9cd1e5a24af0e54342cac66ac669331c/image.png) [log.html](/uploads/b527cfc3344885165a53ae6c4f826aec/log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/159FileNotFoundError: No such file or directory:"schema//Subscriptions.schema.js...2021-06-03T08:49:17ZyaoyuyFileNotFoundError: No such file or directory:"schema//Subscriptions.schema.json" SOL003 VNFLifecycleMangagementAPI v2.6.1When testing subscriptions, we get an error with FileNotFoundError: No such file or directory:"schema//Subscriptions.schema.json".
And checked in the schema folder, there's no file with name Subscriptions.schema.json but have a subscript...When testing subscriptions, we get an error with FileNotFoundError: No such file or directory:"schema//Subscriptions.schema.json".
And checked in the schema folder, there's no file with name Subscriptions.schema.json but have a subscriptions.schema.json.
Maybe the parameter is wrong?https://forge.etsi.org/rep/nfv/api-tests/-/issues/158"=" should not be included in Content range SOL003/SOL005 VNFPackageManagemen...2021-06-03T08:49:17Zyaoyuy"=" should not be included in Content range SOL003/SOL005 VNFPackageManagementAPI V2.6.1When testing APIs with range request, ['Content-Range'] should be equal to ${range}
```
Check HTTP Response Header Content-Range Is Present and Matches the requested range
Log Check Content-Range HTTP Header
Should Contain ...When testing APIs with range request, ['Content-Range'] should be equal to ${range}
```
Check HTTP Response Header Content-Range Is Present and Matches the requested range
Log Check Content-Range HTTP Header
Should Contain ${response['headers']} Content-Range
Should Be Equal As Strings ${response['headers']['Content-Range']} ${range}
Log Header Content-Range is present
```
But in 'Content-Range',"=" should not be included.
(according to the rfc file https://datatracker.ietf.org/doc/rfc7233/?include_text=1)
eg.Content-Range: bytes 21010-47021/47022
Range: bytes=21010-47021/47022https://forge.etsi.org/rep/nfv/api-tests/-/issues/157Unknown parameter value appeared when testing SOL003 VNFPackageManagementAPI ...2021-09-23T01:43:12ZyaoyuyUnknown parameter value appeared when testing SOL003 VNFPackageManagementAPI V2.6.1When testing case 'GET Individual VNF Package Artifact with Range Request and NFVO supporting Range Requests' in VNFPackageArtifacts.robot.
It failed because Content-length(51) is not eqaul to the length parameter's value(1024).
but the ...When testing case 'GET Individual VNF Package Artifact with Range Request and NFVO supporting Range Requests' in VNFPackageArtifacts.robot.
It failed because Content-length(51) is not eqaul to the length parameter's value(1024).
but the value i set to the length parameter is 51, not 1024.
If i run it in local with the same configueration, it can pass[][de6ee3b3-5e77-4c82-ba60-752982a34149.VNFPackageManagement-API.VNFPackageArtifacts.log.html](/uploads/9610bce6031d663f9f5f6a047086f329/de6ee3b3-5e77-4c82-ba60-752982a34149.VNFPackageManagement-API.VNFPackageArtifacts.log.html)[configuration.txt](/uploads/4bebedcb73d62e8363b03380c4a3bc6a/configuration.txt)https://forge.etsi.org/rep/nfv/api-tests/-/issues/156SOL005 Subscription end point is not available for POST response .2021-06-03T08:49:17ZnairaSOL005 Subscription end point is not available for POST response .As part of SOL005 instance creation request , NFVO will create the instance id internally and will do a POST on the subscription end point .
In our testing we created subscription first in NFVO with the generated URL by robo framework
...As part of SOL005 instance creation request , NFVO will create the instance id internally and will do a POST on the subscription end point .
In our testing we created subscription first in NFVO with the generated URL by robo framework
admin@ncs% run show nfv subscriptions
nfv subscriptions ns-subscriptions ns-subscription 06c5a548-24ac-4e10-a99c-95efd15f7c44
callback-uri http://tap.plugtests.net:8111/ecdc80be-5125-45ce-ab04-aa1c99fe8dac
Then we run create instance test
Instance id was created in NFVO and send it to robo as part of API response .
admin@ncs% show nfv ns-info
ns-info b082f6bd-4104-446c-9390-d694572695b5 {
ns-name testNS;
description "NS test from Etsi";
nsd vcu-vcu-nsd;
vnfm-type sol3;
state do-not-instantiate;
}
Same time NFVO will send NsIdentifierCreationNotification to the end point POST to http://tap.plugtests.net:8111/ecdc80be-5125-45ce-ab04-aa1c99fe8dac.
This failed in NFVO. But robo test framework is expecting this notification and it is failing. Attached the logs
On instance:
{'_links': {'instantiate': {'href': 'http://0.0.0.0:9191/nslcm/v1/ns_instances/b082f6bd-4104-446c-9390-d694572695b5/instantiate'},
'self': {'href': 'http://0.0.0.0:9191/nslcm/v1/ns_instances/b082f6bd-4104-446c-9390-d694572695b5'}},
'id': 'b082f6bd-4104-446c-9390-d694572695b5',
'nsInstanceDescription': 'NS test from Etsi',
'nsInstanceName': 'testNS',
'nsState': 'NOT_INSTANTIATED',
'nsdId': 'vcu-vcu-nsd',
'nsdInfoId': 'vcu-vcu-nsd'}
14:07:12.050 FAIL ValidationError: Validation error for schema NsIdentifierCreationNotification.schema.json: 'subscriptionId' is a required property
[6a69eb0e-7199-43b7-81dd-203fd3cb3ce9.NSLifecycleManagement-API.CreateNSInstanceWorkflow.output.xml](/uploads/f34587a436c176c3e4f8decd1f0c9799/6a69eb0e-7199-43b7-81dd-203fd3cb3ce9.NSLifecycleManagement-API.CreateNSInstanceWorkflow.output.xml)
[6a69eb0e-7199-43b7-81dd-203fd3cb3ce9.NSLifecycleManagement-API.CreateNSInstanceWorkflow.report.html](/uploads/03d23c120af61550b0db2d96a79d7df5/6a69eb0e-7199-43b7-81dd-203fd3cb3ce9.NSLifecycleManagement-API.CreateNSInstanceWorkflow.report.html)https://forge.etsi.org/rep/nfv/SOL006/-/issues/33fix AffinityOrAntiAffinityGroup element information in vnfd and nsd2021-03-18T05:55:00Zppreefix AffinityOrAntiAffinityGroup element information in vnfd and nsdv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/32Implement FEAT05 - Add priority in NSD IFA0142021-03-18T05:54:54ZppreeImplement FEAT05 - Add priority in NSD IFA014v3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/api-tests/-/issues/155Typo in SOL005 NSDManagement-API NSDManagementKeywords.robot2021-06-03T08:49:18Zraducccradu@luxoft.comTypo in SOL005 NSDManagement-API NSDManagementKeywords.robot**@{words} = Split String ${NSD_NAME} ,${SEPERATOR}**
should be
**@{words} = Split String ${NSD_NAME} ${SEPARATOR}**
Typo + coma
~"2.6.1" ~"Plu\-2021"**@{words} = Split String ${NSD_NAME} ,${SEPERATOR}**
should be
**@{words} = Split String ${NSD_NAME} ${SEPARATOR}**
Typo + coma
~"2.6.1" ~"Plu\-2021"https://forge.etsi.org/rep/nfv/api-tests/-/issues/154Automated generation of callbackUri notification endpoint during SOL002/3/5 s...2021-06-03T08:49:18ZGiacomo BerniniAutomated generation of callbackUri notification endpoint during SOL002/3/5 subscription operationsAs part of subscriptions operations, the API producer can issue a GET call on the notification endpoint and if the call fails it returns 422.
The test system shall create a notification endpoint and update the callbackUri attribute of su...As part of subscriptions operations, the API producer can issue a GET call on the notification endpoint and if the call fails it returns 422.
The test system shall create a notification endpoint and update the callbackUri attribute of subscription request accordingly.
This is a replication of issue#149https://forge.etsi.org/rep/nfv/api-tests/-/issues/153SOL003/VNFPackageArtifacts/2.6.1 Range is kept all along the test cases2021-10-05T10:15:18ZvignaudSOL003/VNFPackageArtifacts/2.6.1 Range is kept all along the test casesThe first range test case fail for a strange reason :
`GET Individual VNF Package Artifact with Range Request and NFVO supporting Range Requests`
`bytes 0-1023/22872 != bytes=0-1023/22872`
But after that point range is used in :
`Indivi...The first range test case fail for a strange reason :
`GET Individual VNF Package Artifact with Range Request and NFVO supporting Range Requests`
`bytes 0-1023/22872 != bytes=0-1023/22872`
But after that point range is used in :
`Individual VNF Package Artifact with Range Request and NFVO not supporting Range Requests`
Then bad range is set, and used for all other test cases.https://forge.etsi.org/rep/nfv/api-tests/-/issues/152Definition of disk and container format conflicted with Specification v2.6.1 ...2021-02-16T00:56:35ZyaoyuyDefinition of disk and container format conflicted with Specification v2.6.1 SOL003&SOL005 VNFPackageManagementAPIThe definition of disk and container format is conflicted when OpenStack is using lower letters but ETSI is using capitals.
While checking the specification( gs_NFV-SOL003v020401p.pdf and gs_NFV-SOL003v020601p.pdf), it said we should ref...The definition of disk and container format is conflicted when OpenStack is using lower letters but ETSI is using capitals.
While checking the specification( gs_NFV-SOL003v020401p.pdf and gs_NFV-SOL003v020601p.pdf), it said we should refer to the OpenStack.
In chapter 2.2 OpenStack®: "Disk and container formats for images".
error:
ValidationError: Validation error for schema vnfPkgsInfo.schema.json: 'bare' is not one of ['AKI', 'AMI', 'ARI', 'BARE', 'DOCKER', 'OVA', 'OVF']https://forge.etsi.org/rep/nfv/api-tests/-/issues/151When ${NFVO_RANGE_OK} =1 , test case 'XXX and NFVO not supporting Range Reque...2021-06-03T08:49:18ZyaoyuyWhen ${NFVO_RANGE_OK} =1 , test case 'XXX and NFVO not supporting Range Requests' should be skipped SOL003 v2.6.1 VNFPackage ManagementAPIWhen testing the whole test suite 'VNFPackageContent.robot', if ${NFVO_RANGE_OK} is set to 1, both supporting and not-supporting cases will be tested. However, if ${NFVO_RANGE_OK} is set to 0, both cases will be skipped. (This situation ...When testing the whole test suite 'VNFPackageContent.robot', if ${NFVO_RANGE_OK} is set to 1, both supporting and not-supporting cases will be tested. However, if ${NFVO_RANGE_OK} is set to 0, both cases will be skipped. (This situation also happens in VNFPackageArtifacts.robot)https://forge.etsi.org/rep/nfv/api-tests/-/issues/150Missing Set Suite Variable in keyword 'Check Postcondition VNF Package Artif...2021-02-08T11:01:31ZyaoyuyMissing Set Suite Variable in keyword 'Check Postcondition VNF Package Artifact Exist' v2.6.1 SOL003&SOL005 VNFPackageManagement-API```
Check Postcondition VNF Package Artifact Exist
Log Checking that vnf pacakge still exists
Set Headers {"Accept": "${ACCEPT_JSON}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization": "${AUTHORIZ...```
Check Postcondition VNF Package Artifact Exist
Log Checking that vnf pacakge still exists
Set Headers {"Accept": "${ACCEPT_JSON}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization": "${AUTHORIZATION}"}
GET ${apiRoot}/${apiName}/${apiVersion}/vnf_packages/${vnfPackageId}/artifacts/${artifactPath}
Check HTTP Response Status Code Is 200
```
because
```
${output}= Output response
Set Suite Variable ${response} ${output}
```
is missing after the API request, so when checking the http code, the api response which is from delete api request is used.https://forge.etsi.org/rep/nfv/api-tests/-/issues/149SOL005 NS Subscription END point is returning 404 for GET response.2021-02-15T08:36:38ZnairaSOL005 NS Subscription END point is returning 404 for GET response.As part of LccnSubscriptionRequest , NFVO will make a GET call on the notification end point and if the call fails , NFVO will return with a 422.
The test framework is not handling this scenario and test is failing . Test Details attache...As part of LccnSubscriptionRequest , NFVO will make a GET call on the notification end point and if the call fails , NFVO will return with a 422.
The test framework is not handling this scenario and test is failing . Test Details attached
To Proceed this NFVO needs a succesful GET Response from the end point , then only subscription will be created .[c5de62bb-c774-45ec-b969-bcc11fb19fc4.NSLifecycleManagement-API.Subscriptions.log.html](/uploads/ad3b5a51feafa6fb470cca18abfb20c8/c5de62bb-c774-45ec-b969-bcc11fb19fc4.NSLifecycleManagement-API.Subscriptions.log.html)
[suetsi@localhost payloads]$ curl -X GET http://tap.plugtests.net:8111/c5de62bb-c774-45ec-b969-bcc11fb19fc4 -v
* About to connect() to tap.plugtests.net port 8111 (#0)
* Trying 212.234.160.71...
* Connected to tap.plugtests.net (212.234.160.71) port 8111 (#0)
> GET /c5de62bb-c774-45ec-b969-bcc11fb19fc4 HTTP/1.1
> User-Agent: curl/7.29.0
> Host: tap.plugtests.net:8111
> Accept: */*
>
< HTTP/1.1 404 Not Found
< content-length: 0
< connection: keep-alive
<
* Connection #0 to host tap.plugtests.net left intacthttps://forge.etsi.org/rep/nfv/SOL002-SOL003/-/issues/1Invalid API version endpoint2021-02-05T17:27:59ZGiacomo BerniniInvalid API version endpointAccording to SOL 013 (https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/013/02.06.01_60/gs_nfv-sol013v020601p.pdf) the endpoint should have an underscore, not a hyphen:
`/api-versions` should `/api_versions`
replica of: https://forg...According to SOL 013 (https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/013/02.06.01_60/gs_nfv-sol013v020601p.pdf) the endpoint should have an underscore, not a hyphen:
`/api-versions` should `/api_versions`
replica of: https://forge.etsi.org/rep/nfv/SOL005/issues/3