api-tests issueshttps://forge.etsi.org/rep/nfv/api-tests/-/issues2021-01-28T17:35:47Zhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/133The parameter ${vnfLcmOpOccId} is defined repetitiously in the variables.txt ...2021-01-28T17:35:47ZyaoyuyThe parameter ${vnfLcmOpOccId} is defined repetitiously in the variables.txt file and the configuration.txt fileThe parameter ${vnfLcmOpOccId} is defined repetitiously in the variables.txt file and the configuration.txt file.
From what we thought, only the global parameter like HOST IP are defined in the configuration.txt,
so when testing , we on...The parameter ${vnfLcmOpOccId} is defined repetitiously in the variables.txt file and the configuration.txt file.
From what we thought, only the global parameter like HOST IP are defined in the configuration.txt,
so when testing , we only changed the vnfLcmOpOccId in variables.txt file and met the error resource not found with not changing the vnfLcmOpOccId in the configuration.txt file .https://forge.etsi.org/rep/nfv/api-tests/-/issues/134Inconsistency in MockServer configuration parameters2021-01-19T15:51:12ZMichele CarignaniInconsistency in MockServer configuration parametersIt appears that the config variables for Mockserver are sometimes used differently, e.g. sometimes they are used independently:
```
*** Keywords ***
Create Sessions
Start Process java -jar ${MOCK_SERVER_JAR} -serverPort ${callb...It appears that the config variables for Mockserver are sometimes used differently, e.g. sometimes they are used independently:
```
*** Keywords ***
Create Sessions
Start Process java -jar ${MOCK_SERVER_JAR} -serverPort ${callback_port} alias=mockInstance
Wait For Process handle=mockInstance timeout=5s on_timeout=continue
Create Mock Session ${callback_uri}:${callback_port}
```
SOL003 vnf inicator api variables:
```
${callback_uri} http://localhost
${callback_port} 9091
```
while some other times:
```
Send Post Request for VNF Package Subscription
Log Trying to create a new subscription
Set Headers {"Accept": "${ACCEPT_JSON}"}
Set Headers {"Content-Type": "${CONTENT_TYPE_JSON}"}
${template}= Get File jsons/subscriptions.json
${body}= Format String ${template} callback_uri=${callback_uri} callback_endpoint=${callback_endpoint} vnfPkgId=${vnfPkgId} **<- assumes port is included in the uri **
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization": "${AUTHORIZATION}"}
POST ${apiRoot}/${apiName}/${apiMajorVersion}/subscriptions ${body}
${output}= Output response
Set Suite Variable ${response} ${output}
Run Keyword If ${NFVO_CHECKS_NOTIF_ENDPOINT} == 1
... Check Notification Endpoint
Create Sessions
Pass Execution If ${NFVO_CHECKS_NOTIF_ENDPOINT} == 0 MockServer not started as NFVO is not checking the notification endpoint
Start Process java -jar ${MOCK_SERVER_JAR} -serverPort ${callback_port} alias=mockInstance
Wait For Process handle=mockInstance timeout=5s on_timeout=continue
Create Mock Session ${callback_uri} **<- assumes port is included in the uri**
```
My understanding would be that the correct version to be supported is the one with `${callback_uri}:${callback_port}`.Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/135SOL003 / VNF LCM - conflicting operations on vnf instances2021-06-03T08:49:18ZMichele CarignaniSOL003 / VNF LCM - conflicting operations on vnf instances## HealVNFTask
Test suite tries to send heal POST to an instantiated VNF, and after that, it tries to heal a not instantiated VNF, and uses the same ID
## IndividualVNFInstance
DELETE testing is controversial: both DELETE case uses th...## HealVNFTask
Test suite tries to send heal POST to an instantiated VNF, and after that, it tries to heal a not instantiated VNF, and uses the same ID
## IndividualVNFInstance
DELETE testing is controversial: both DELETE case uses the same VNF ID, but with different pre-conditions, and if the first DELETE is successful (which is expected by the test), the VNF does not exist by the time the following DELETE test case is running
https://forge.etsi.org/rep/nfv/api-tests/-/issues/136Non utf-8 charachters present in schema json SOL003 VNFLifecyManagement-API2021-02-04T18:31:52Zraducccradu@luxoft.comNon utf-8 charachters present in schema json SOL003 VNFLifecyManagement-APIAfter running a command to highlight non utf-8 charachters:
grep -axv '.*' schemas/VnfLcmOperationOccurrenceNotification.schema.json
"description": "If present, this attribute signals modifications of the \"vnfProvider\" ...After running a command to highlight non utf-8 charachters:
grep -axv '.*' schemas/VnfLcmOperationOccurrenceNotification.schema.json
"description": "If present, this attribute signals modifications of the \"vnfProvider\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfPkgId\" attribute) was modified implicitly following a request to modify the \"vnfPkgId\" attribute, by copying the value of this attribute from the VNFD in the VNF Package identified by the \"vnfPkgId� attribute.\n",
"description": "If present, this attribute signals modifications of the \"vnfProductName\" attribute in \"VnfInstance\". If present, this attribute (which depends on the value of the \"vnfPkgId\" attribute) was modified implicitly following a request to modify the \"vnfPkgId\" attribute, by copying the value of this attribute from the VNFD in the VNF Package identified by the \"vnfPkgId� attribute.\n",
Get File(HealVNFWorkflow.robot) run keyword fails because of thishttps://forge.etsi.org/rep/nfv/api-tests/-/issues/137Separator argument missing in SOL003 VNFFaultManagement-API ApiVersion.robot2021-01-27T15:42:33Zraducccradu@luxoft.comSeparator argument missing in SOL003 VNFFaultManagement-API ApiVersion.robot${schema} = Catenate ${input} .schema.json
should be
${schema} = Catenate SEPARATOR= ${input} .schema.json${schema} = Catenate ${input} .schema.json
should be
${schema} = Catenate SEPARATOR= ${input} .schema.jsonhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/138Separator argument missing in SOL003 VNFPackageManagement-API ApiVersion.robot2021-01-27T15:42:24Zraducccradu@luxoft.comSeparator argument missing in SOL003 VNFPackageManagement-API ApiVersion.robot${schema} = Catenate ${input} .schema.json
should be
${schema} = Catenate SEPARATOR= ${input} .schema.json${schema} = Catenate ${input} .schema.json
should be
${schema} = Catenate SEPARATOR= ${input} .schema.jsonhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/139Separator argument missing in SOL005 NSDManagement-API ApiVersion.robot2021-01-27T15:42:07Zraducccradu@luxoft.comSeparator argument missing in SOL005 NSDManagement-API ApiVersion.robot${schema} = Catenate ${input} .schema.json
should be
${schema} = Catenate SEPARATOR= ${input} .schema.json${schema} = Catenate ${input} .schema.json
should be
${schema} = Catenate SEPARATOR= ${input} .schema.jsonhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/140Wrong Keywords in SOL003 VNFPackageManagement-API VNFPackageContent.robot2021-02-04T18:31:52ZyaoyuyWrong Keywords in SOL003 VNFPackageManagement-API VNFPackageContent.robotTest case as follows:
POST Individual VNF Package Content - Method not implemented
PUT Individual VNF Package Content - Method not implemented
PATCH Individual VNF Package Content - Method not implemented
DELETE Individual VNF Package Co...Test case as follows:
POST Individual VNF Package Content - Method not implemented
PUT Individual VNF Package Content - Method not implemented
PATCH Individual VNF Package Content - Method not implemented
DELETE Individual VNF Package Content - Method not implemented
is using keywords:
Send POST Request for individual VNF Package
Send PUT Request for individual VNF Package
Send PATCH Request for individual VNF Package
Send DELETE Request for individual VNF Package
these should be
Send POST Request for individual VNF Package Content
Send PUT Request for individual VNF Package Content
Send PATCH Request for individual VNF Package Content
Send DELETE Request for individual VNF Package Contenthttps://forge.etsi.org/rep/nfv/api-tests/-/issues/142Separator argument missing 2.6.12021-02-04T18:31:52Zraducccradu@luxoft.comSeparator argument missing 2.6.1Target file: SOL003/VNFFaultManagement-API/FaultManagement-APIKeyword.robot
${schema} = Catenate ${input} .schema.json
should be
${schema} = Catenate SEPARATOR= ${input} .schema.json
\~"2.6.1" \~"Plu\-2021" Target file: SOL003/VNFFaultManagement-API/FaultManagement-APIKeyword.robot
${schema} = Catenate ${input} .schema.json
should be
${schema} = Catenate SEPARATOR= ${input} .schema.json
\~"2.6.1" \~"Plu\-2021" https://forge.etsi.org/rep/nfv/api-tests/-/issues/143Wrong parameter name in 'IndividualVnfLcmOperationOccurence.robot' SOL003 VN...2021-02-03T14:11:51ZyaoyuyWrong parameter name in 'IndividualVnfLcmOperationOccurence.robot' SOL003 VNFLifecycleManagement-API v2.6.1The parameter value offerd to 'Check HTTP Response Body Json Schema Is' in test case 'Get information about multiple VNF instances' is VnfLcmOpOcc.
But there is no such file named by VnfLcmOpOcc in shema folder. (maybe the value need be ...The parameter value offerd to 'Check HTTP Response Body Json Schema Is' in test case 'Get information about multiple VNF instances' is VnfLcmOpOcc.
But there is no such file named by VnfLcmOpOcc in shema folder. (maybe the value need be changed to VnfLcmOpOcc or vnfLcmOpOccs?)https://forge.etsi.org/rep/nfv/api-tests/-/issues/144Wrong method in Keywords 'GET Scale vnfInstance' SOL003 VNFLifecycleManagem...2021-01-28T10:45:32ZyaoyuyWrong method in Keywords 'GET Scale vnfInstance' SOL003 VNFLifecycleManagement-API v2.6.1In Keywords GET Scale vnfInstance
Post ${apiRoot}/${apiName}/${apiVersion}/vnf_instances/${vnfInstanceId}/scale
should be
GET ${apiRoot}/${apiName}/${apiVersion}/vnf_instances/${vnfInstanceId}/scale
and no body is neededIn Keywords GET Scale vnfInstance
Post ${apiRoot}/${apiName}/${apiVersion}/vnf_instances/${vnfInstanceId}/scale
should be
GET ${apiRoot}/${apiName}/${apiVersion}/vnf_instances/${vnfInstanceId}/scale
and no body is neededhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/146Misplaced referenced json requests in VNFPackageManagementKeywords.robot2021-02-03T18:29:30Zraducccradu@luxoft.comMisplaced referenced json requests in VNFPackageManagementKeywords.robot**SOL005/VNFPackageManagement-API/VNFPackageManagementKeywords.robot**
`Send PATCH to disable Individual VNF Package`
**`${body}= Get File jsons/NsdInfoModificationDisable.json`**
`Send PATCH to enable Individual VNF Package`
...**SOL005/VNFPackageManagement-API/VNFPackageManagementKeywords.robot**
`Send PATCH to disable Individual VNF Package`
**`${body}= Get File jsons/NsdInfoModificationDisable.json`**
`Send PATCH to enable Individual VNF Package`
`${body}= Get File jsons/NsdInfoModificationEnable.json`
~"2.6.1" ~"Plu\-2021"
https://forge.etsi.org/rep/nfv/api-tests/-/issues/147Wrong parameter vlalue in 'Get all VNF Packages with malformed authorization ...2021-02-12T08:57:46ZyaoyuyWrong parameter vlalue in 'Get all VNF Packages with malformed authorization token' SOL005 VNFPackges.robot V2.6.1When we get all VNF Packages Information with malformed authorization token, the api will return a result as 'unauthorziated'.
So when checking the http status code, i think it should be 401, not 400When we get all VNF Packages Information with malformed authorization token, the api will return a result as 'unauthorziated'.
So when checking the http status code, i think it should be 401, not 400https://forge.etsi.org/rep/nfv/api-tests/-/issues/148JSON schemas containing references to external files2021-06-03T08:49:18ZMichele CarignaniJSON schemas containing references to external filesSpotted in `subscriptions.schema.json` for SOL005/NS_LCM_API/schemas`. The file contains:
```
"properties": {
"self": {
"description": "URI of this resource.\n",
"$ref": "SOL005_def.yaml#/definitions/Link"
}
}
```
but the referen...Spotted in `subscriptions.schema.json` for SOL005/NS_LCM_API/schemas`. The file contains:
```
"properties": {
"self": {
"description": "URI of this resource.\n",
"$ref": "SOL005_def.yaml#/definitions/Link"
}
}
```
but the references `SOL005_def.yaml` should have been resolved.
## Affected files
List created with `$ grep 'SOL005_def.yaml' -r | cut -d: -f1 | sort | uniq` in the branch `2.4.1-fix-plu`.
* [x] SOL005/NSFaultManagement-API/schemas/FaultyComponentInfo.schema.json
* [x] SOL005/NSFaultManagement-API/schemas/FaultyResourceInfo.schema.json
* [x] SOL005/NSFaultManagement-API/schemas/FmNotificationsFilter.schema.json
* [x] SOL005/NSFaultManagement-API/schemas/FmSubscription.schema.json
* [x] SOL005/NSFaultManagement-API/schemas/FmSubscriptionRequest.schema.json
* [x] SOL005/NSFaultManagement-API/schemas/alarm.schema.json
* [x] SOL005/NSFaultManagement-API/schemas/alarmClearedNotification.schema.json
* [x] SOL005/NSFaultManagement-API/schemas/alarmListRebuiltNotification.schema.json
* [x] SOL005/NSFaultManagement-API/schemas/alarmNotification.schema.json
* [x] SOL005/NSLifecycleManagement-API/jsons/CreateNsRequest.json
* [x] SOL005/NSLifecycleManagement-API/jsons/InstantiateNsRequest.json
* [x] SOL005/NSLifecycleManagement-API/jsons/ScaleNsRequest.json
* [x] SOL005/NSLifecycleManagement-API/jsons/UpdateNsRequest.json
* [x] SOL005/NSLifecycleManagement-API/schemas/NsIdentifierCreationNotification.schema.json
* [x] SOL005/NSLifecycleManagement-API/schemas/NsIdentifierDeletionNotification.schema.json
* [x] SOL005/NSLifecycleManagement-API/schemas/NsLcmOperationOccurrenceNotification.schema.json
* [x] SOL005/NSLifecycleManagement-API/schemas/subscription.schema.json
* [x] SOL005/NSLifecycleManagement-API/schemas/subscriptions.schema.jsonhttps://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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/166Wrong data type for links SOL005 VNFPackageManagementAPI v2.6.12021-06-03T08:49:17ZyaoyuyWrong data type for links SOL005 VNFPackageManagementAPI v2.6.1Test failed beacause meeting the error as followed:
ValidationError: Validation error for schema links.schema.json: {'self': {'href': '/vnfpkgm/v1/vnf_packages/04d7a289-50d7-42c6-bcab-795712f0c3a5'}, 'packageContent': {'href': '/vnfpkgm/...Test failed beacause meeting the error as followed:
ValidationError: Validation error for schema links.schema.json: {'self': {'href': '/vnfpkgm/v1/vnf_packages/04d7a289-50d7-42c6-bcab-795712f0c3a5'}, 'packageContent': {'href': '/vnfpkgm/v1/vnf_packages/04d7a289-50d7-42c6-bcab-795712f0c3a5/package_content'}} is not of type 'array'
refered to the links.schema.json file, the code is
`"type": "array",`
but according to the sol specification (SOL005 v2.6.1 9.5.2.5 Type: VnfPkgInfo), the links's data type should be Structure (inlined)
[249cd2b9-168c-4272-80ff-0d348154432c.VNFPackageManagement-API.VNFPackages.log.html](/uploads/0e4260747fe1eabc4af0a4475b20f9de/249cd2b9-168c-4272-80ff-0d348154432c.VNFPackageManagement-API.VNFPackages.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/167POST Terminate a vnfInstance Conflict returned http code 202 SOL003 VNFLifecy...2021-06-03T08:49:17ZyaoyuyPOST Terminate a vnfInstance Conflict returned http code 202 SOL003 VNFLifecycleManagementAPI v2.6.1According to the specifitiaction, when termanting a not-instantiate state vnf instance, it should return http code 409, while the code check if it is 202.
specificaition SOL003 V2.6.1 Chapter 5.4.8.3.1
Typically, this is due to the fact...According to the specifitiaction, when termanting a not-instantiate state vnf instance, it should return http code 409, while the code check if it is 202.
specificaition SOL003 V2.6.1 Chapter 5.4.8.3.1
Typically, this is due to the fact that the "Individual VNF
instance" resource is in NOT_INSTANTIATED state,
that another lifecycle management operation is
ongoing, or that a required (see note) child attribute of
the "extensions" attribute has not been set.https://forge.etsi.org/rep/nfv/api-tests/-/issues/168TST issue in '/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs SOL003 v2.6.1 api2021-03-09T14:17:25ZguptanavTST issue in '/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs SOL003 v2.6.1 apiwhen testing **/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs SOL003** api
HTTP return code is 200 but test suite is fail as it is expecting 202 return code
[ocss_TST_ISSUE.txt](/uploads/e8d79d9fe5cd48e124226acae9be210b/ocss_TST_ISSUE.txt)when testing **/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs SOL003** api
HTTP return code is 200 but test suite is fail as it is expecting 202 return code
[ocss_TST_ISSUE.txt](/uploads/e8d79d9fe5cd48e124226acae9be210b/ocss_TST_ISSUE.txt)https://forge.etsi.org/rep/nfv/api-tests/-/issues/169SOL005 NS LCM Individual NSInstance v2.7.1 - delete with conflict cannot be r...2021-03-03T17:59:25ZGiacomo BerniniSOL005 NS LCM Individual NSInstance v2.7.1 - delete with conflict cannot be run due to previous test executionThis test uses a single nsInstanceId variable, however, when it gets deleted at the “delete” test, then it can’t be found at the “delete conflict” testThis test uses a single nsInstanceId variable, however, when it gets deleted at the “delete” test, then it can’t be found at the “delete conflict” testhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/170SOL002 /vnflcm/{apiMajorVersion}/vnf_instances POST, /vnflcm/{apiMajorVersion...2021-05-28T07:11:16ZguptanavSOL002 /vnflcm/{apiMajorVersion}/vnf_instances POST, /vnflcm/{apiMajorVersion}/vnf_instances GET and /vnflcm/{apiMajorVersion}/vnf_instances/${vnfInstanceId} GET V2.6.1When testing cases
* '**Create a new vnfInstance**' some validation error for schema vnfInstance.schema.json: '*vnfPkgInfoId*' is a required property comes but HTTP return status is 201
* '**GET information about multiple VNF insta...When testing cases
* '**Create a new vnfInstance**' some validation error for schema vnfInstance.schema.json: '*vnfPkgInfoId*' is a required property comes but HTTP return status is 201
* '**GET information about multiple VNF instances**' some validation error for schema vnfInstance.schema.json: '*vnfPkgInfoId*' is a required property comes but HTTP return status is 201
* '**Get Information about an individual VNF Instance**' some validation error for schema vnfInstance.schema.json: '*vnfPkgInfoId*' is a required property comes but HTTP return status is 200
*Attached are complete logs of the same* :
[82461eeb-3b91-49b0-b713-9f177d06e830.VNFLifecycleManagement-API.VNFInstances.log.html](/uploads/fe2c3cf96711fd950ab429de66f8d8e4/82461eeb-3b91-49b0-b713-9f177d06e830.VNFLifecycleManagement-API.VNFInstances.log.html)[d7ccf875-e3c1-4823-a5fa-6f6e21790574.VNFLifecycleManagement-API.IndividualVNFInstance.log.html](/uploads/bdde85d95aa68e13898197f9a2b25354/d7ccf875-e3c1-4823-a5fa-6f6e21790574.VNFLifecycleManagement-API.IndividualVNFInstance.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/171SOL002 /vnflcm/{apiMajorVersion}/vnf_lcm_op_occs, /vnflcm/{apiMajorVersion}/v...2021-05-28T07:11:07ZguptanavSOL002 /vnflcm/{apiMajorVersion}/vnf_lcm_op_occs, /vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId}, /vnflcm/{apiMajorVersion}/subscriptions and /vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId} GET V2.6.1When testing cases
* '**GET status information about multiple VNF LCM operation occurrences**'
* '**Get information about multiple VNF instances**
* '**GET Subscriptions**'
* '**GET Individual Subscription**'
they all got fai...When testing cases
* '**GET status information about multiple VNF LCM operation occurrences**'
* '**Get information about multiple VNF instances**
* '**GET Subscriptions**'
* '**GET Individual Subscription**'
they all 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* :
[1011cde5-cbc8-4e78-abae-7f1e04825cde.VNFLifecycleManagement-API.VnfLcmOperationOccurences.log.html](/uploads/2ca2ec54d04c7e8bd9ad493b66a4a1a2/1011cde5-cbc8-4e78-abae-7f1e04825cde.VNFLifecycleManagement-API.VnfLcmOperationOccurences.log.html)[e040fbc1-df19-4e79-a62a-1920dc7d9649.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html](/uploads/ac24de9919bac234e6149aa8ad3294c6/e040fbc1-df19-4e79-a62a-1920dc7d9649.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html)[a1d86506-aee1-4893-ba5b-368a4e0a2f8c.VNFLifecycleManagement-API.Subscriptions.log.html](/uploads/59eb245f335e2fa95b7c48e37c9c0b83/a1d86506-aee1-4893-ba5b-368a4e0a2f8c.VNFLifecycleManagement-API.Subscriptions.log.html)[8fd09181-deab-44dd-84f4-b5d96f391396.VNFLifecycleManagement-API.IndividualSubscription.log.html](/uploads/708c1228e41dbbcf897ede19b5953c51/8fd09181-deab-44dd-84f4-b5d96f391396.VNFLifecycleManagement-API.IndividualSubscription.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/172SOL002 /vnflcm/{apiMajorVersion}/subscriptions POST V2.6.12021-03-18T06:28:46ZguptanavSOL002 /vnflcm/{apiMajorVersion}/subscriptions POST V2.6.1When testing cases' **POST Create a new 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* :
[...When testing cases' **POST Create a new 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* :
[a1d86506-aee1-4893-ba5b-368a4e0a2f8c.VNFLifecycleManagement-API.Subscriptions.log.html](/uploads/2ac94ad8afddc6eb3f47fb87a88c9567/a1d86506-aee1-4893-ba5b-368a4e0a2f8c.VNFLifecycleManagement-API.Subscriptions.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/173SOL002 and SOL003 /vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId} D...2021-05-28T07:11:32ZguptanavSOL002 and SOL003 /vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId} DELETE V2.6.1When testing cases' '**DELETE an individual subscription**' HIVE TAP return 204 but expected is 405
*Attached are complete logs of the same* :
[8fd09181-deab-44dd-84f4-b5d96f391396.VNFLifecycleManagement-API.IndividualSubscription.log...When testing cases' '**DELETE an individual subscription**' HIVE TAP return 204 but expected is 405
*Attached are complete logs of the same* :
[8fd09181-deab-44dd-84f4-b5d96f391396.VNFLifecycleManagement-API.IndividualSubscription.log.html](/uploads/8bc7401b73e41327fb16f4f1bbe40ba7/8fd09181-deab-44dd-84f4-b5d96f391396.VNFLifecycleManagement-API.IndividualSubscription.log.html)
[fd116d50-052f-475c-9fb0-5fc382afdd73.VNFLifecycleManagement-API.IndividualSubscription.log.html](/uploads/275995211db731eeaf15f81f8536e16d/fd116d50-052f-475c-9fb0-5fc382afdd73.VNFLifecycleManagement-API.IndividualSubscription.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/174SOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId}/fail API POS...2021-06-03T08:49:17ZguptanavSOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId}/fail API POST V2.6.1When testing case 'POST Fail operation task' some Internal Server Error and Can not find requested vnf instance
*Attached are complete logs of the same* :
[a05010be-3af1-4aa1-b331-03d6659b9b1d.VNFLifecycleManagement-API.FailOperationT...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* :
[a05010be-3af1-4aa1-b331-03d6659b9b1d.VNFLifecycleManagement-API.FailOperationTask.log.html](/uploads/85820332f35826f2c631de05e92cff32/a05010be-3af1-4aa1-b331-03d6659b9b1d.VNFLifecycleManagement-API.FailOperationTask.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/175SOL003 and SOL002 /vnflcm/{apiMajorVersion}/vnf_instances/${vnfInstanceId} GE...2021-05-28T07:11:41ZguptanavSOL003 and SOL002 /vnflcm/{apiMajorVersion}/vnf_instances/${vnfInstanceId} GET V2.4.1When testing case '**Get Information about an individual VNF Instance**' some 'Expected property 'response headers ETag' was not found.' comes but HTTP return status is 200
*Attached are complete logs of the same* :
[e07f6a91-4872-459c...When testing case '**Get Information about an individual VNF Instance**' some 'Expected property 'response headers ETag' was not found.' comes but HTTP return status is 200
*Attached are complete logs of the same* :
[e07f6a91-4872-459c-b148-824e5dae8802.VNFLifecycleManagement-API.IndividualVNFInstance.log.html](/uploads/c9b6f7e4d29402f814241dc7ff88e32a/e07f6a91-4872-459c-b148-824e5dae8802.VNFLifecycleManagement-API.IndividualVNFInstance.log.html)
[1b94e0bb-0d8e-459d-b585-27c0d759e7a9.VNFLifecycleManagement-API.IndividualVNFInstance.log.html](/uploads/fcc88ad00ae8a612c184c2aba209ae5d/1b94e0bb-0d8e-459d-b585-27c0d759e7a9.VNFLifecycleManagement-API.IndividualVNFInstance.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/176SOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs V2.4.1 GET method2021-05-28T07:11:24ZguptanavSOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs V2.4.1 GET methodWhen testing case '**GET status information about multiple VNF LCM operation occurrences**' HTTP return status is 200 but expected is 202
*Attached are complete logs of the same* :
[8c9344dd-510f-4985-89fc-f3cbcbf89bf5.VNFLifecycleMan...When testing case '**GET status information about multiple VNF LCM operation occurrences**' HTTP return status is 200 but expected is 202
*Attached are complete logs of the same* :
[8c9344dd-510f-4985-89fc-f3cbcbf89bf5.VNFLifecycleManagement-API.VnfLcmOperationOccurences.log.html](/uploads/aae5da20875d22faac95ceeeb09095ee/8c9344dd-510f-4985-89fc-f3cbcbf89bf5.VNFLifecycleManagement-API.VnfLcmOperationOccurences.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)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/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/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/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/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)