NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2019-02-21T10:59:51Zhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/1Response code and typos on SOL002/VNFConfiguration-API/Configuration.robot2019-02-21T10:59:51ZElian KrajaResponse code and typos on SOL002/VNFConfiguration-API/Configuration.robotWhen executing VNFConfiguration-API/Configuration.robot the Keyword Check HTTP Response Status Code Is fails with the following message:
Resolving variable '${response.status_code}' failed: AttributeError: 'str' object has no attribute ...When executing VNFConfiguration-API/Configuration.robot the Keyword Check HTTP Response Status Code Is fails with the following message:
Resolving variable '${response.status_code}' failed: AttributeError: 'str' object has no attribute 'status_code'
There is also a typo in the files. The folder containing jsons is named jsons in the repo, but refered as json in the file.
FileNotFoundError: [Errno 2] No such file or directory: 'testsuites/VNFConfiguration-API/json/vnfConfigModifications.json'Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/2Missing variable on NEG_AUTHORIZATION in SOL002/VNFIndicator-API/VNFIndicator...2019-02-21T10:59:48ZElian KrajaMissing variable on NEG_AUTHORIZATION in SOL002/VNFIndicator-API/VNFIndicators.robotIn the VNFIndicators test, the variable NEG_AUTHORIZATION is missing from the variables.txt file
Test fails with: Variable '${NEG_AUTHORIZATION}' not found.In the VNFIndicators test, the variable NEG_AUTHORIZATION is missing from the variables.txt file
Test fails with: Variable '${NEG_AUTHORIZATION}' not found.Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/3Typo on SOL002/VNFIndicator-API/Subscriptions.robot2019-02-21T10:59:43ZElian KrajaTypo on SOL002/VNFIndicator-API/Subscriptions.robotThe folder jsons is referred as json in the Subscriptions.robot file.
The test fails with the following error:
FileNotFoundError: [Errno 2] No such file or directory: 'testsuites/VNFIndicator-API/json/subscriptions.json'The folder jsons is referred as json in the Subscriptions.robot file.
The test fails with the following error:
FileNotFoundError: [Errno 2] No such file or directory: 'testsuites/VNFIndicator-API/json/subscriptions.json'Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/4Missing "response body" when filtering response for DELETE operation on SOL00...2019-02-21T10:59:39ZElian KrajaMissing "response body" when filtering response for DELETE operation on SOL002/VNFIndicator-API/IndividualSubscription.robotThe Validate json fails with:
ValidationError: Validation error for schema ProblemDetails.schema.json: 'status' is a required property
The issue is raised because the checking is done on the full json of the response, not only on the b...The Validate json fails with:
ValidationError: Validation error for schema ProblemDetails.schema.json: 'status' is a required property
The issue is raised because the checking is done on the full json of the response, not only on the body part, as expected.Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/5Issue with Request Methods, robot script not allowing POST,PUT,PATCH,DELETE r...2019-02-21T10:59:35ZjonnadaIssue with Request Methods, robot script not allowing POST,PUT,PATCH,DELETE requests in SOL003/VNFFaultManagement-API/Alarms.robot'request':
- 'method':
- "Request was not one of the allowed request methods. Got `post`: Expected one of: `{'get'}`
'request':
- 'method':
- "Request was not one of the allowed request methods. Got `put`: Expect...'request':
- 'method':
- "Request was not one of the allowed request methods. Got `post`: Expected one of: `{'get'}`
'request':
- 'method':
- "Request was not one of the allowed request methods. Got `put`: Expected one of: `{'get'}`"
'request':
- 'method':
- "Request was not one of the allowed request methods. Got `patch`: Expected one of: `{'get'}`"
request':
- 'method':
- "Request was not one of the allowed request methods. Got `delete`: Expected one of: `{'get'}`"
https://forge.etsi.org/rep/nfv/api-tests/-/issues/6Robot script expecting object types instead of arrays in SOL003/VNFFaultManag...2019-02-21T10:59:30ZjonnadaRobot script expecting object types instead of arrays in SOL003/VNFFaultManagement-API/Alarms.robot'response':
- 'body':
- 'schema':
- '$ref':
- 'type':
- "Got value `[]` of type `array`. Value must be of type(s): `('object',)`"'response':
- 'body':
- 'schema':
- '$ref':
- 'type':
- "Got value `[]` of type `array`. Value must be of type(s): `('object',)`"https://forge.etsi.org/rep/nfv/api-tests/-/issues/7Robot script is expecting 200 for POST, PUT, PATCH where 405 should be expect...2019-02-21T10:59:25ZjonnadaRobot script is expecting 200 for POST, PUT, PATCH where 405 should be expected as per SOL003 Spec in VNFFaultManagement-API/IndividualSubscription.robotParent suite setup failed:
405 is not one of [200]
Failed validating 'enum' in schema:
{'enum': [200], 'type': 'integer'}
On instance:
405Parent suite setup failed:
405 is not one of [200]
Failed validating 'enum' in schema:
{'enum': [200], 'type': 'integer'}
On instance:
405https://forge.etsi.org/rep/nfv/api-tests/-/issues/8Missing Java and required packages on test system SOL003/VNFFaultManagementNo...2019-02-21T10:56:52ZjonnadaMissing Java and required packages on test system SOL003/VNFFaultManagementNotification-API/NotificatinEndpoint.robotError in file '/opt/PLU/VNFM_R-VNFM_ERICSSON_20190214_1/testsuites/VNFFaultManagementNotification-API/NotificationEndpoint.robot': Importing test library 'MockServerLibrary' failed: ImportError: No module named 'MockServerLibrary'
Traceb...Error in file '/opt/PLU/VNFM_R-VNFM_ERICSSON_20190214_1/testsuites/VNFFaultManagementNotification-API/NotificationEndpoint.robot': Importing test library 'MockServerLibrary' failed: ImportError: No module named 'MockServerLibrary'
Traceback (most recent call last):
None
PYTHONPATH:
/usr/local/bin
/usr/lib/python35.zip
/usr/lib/python3.5
/usr/lib/python3.5/plat-x86_64-linux-gnu
/usr/lib/python3.5/lib-dynload
/usr/local/lib/python3.5/dist-packages
/usr/local/lib/python3.5/dist-packages/jsonpath-0.80-py3.5.egg
/home/elian/robotframework-jsonlibrary
/usr/lib/python3/dist-packageshttps://forge.etsi.org/rep/nfv/api-tests/-/issues/9Robot script expecting object instead of an array in SOL003/VNFFaultManagemen...2019-02-21T10:56:57ZjonnadaRobot script expecting object instead of an array in SOL003/VNFFaultManagement-API/Subscriptions.robotExample:
Got value `[{'callbackUri': 'http://127.0.0.1/subscribe', 'id': '0e74eb86-303b-11e9-b638-fa163ec3fde3'}, {'callbackUri': 'https://127.0.0.1:8048/alarm_notifications', 'id': '0c556460-303c-11e9-a0f9-fa163ec3fde3'}, {'callbackUri...Example:
Got value `[{'callbackUri': 'http://127.0.0.1/subscribe', 'id': '0e74eb86-303b-11e9-b638-fa163ec3fde3'}, {'callbackUri': 'https://127.0.0.1:8048/alarm_notifications', 'id': '0c556460-303c-11e9-a0f9-fa163ec3fde3'}, {'callbackUri': 'https://127.0.0.1:8048/alarm_notifications', 'id': 'bff676cc-3027-11e9-811b-fa163ec3fde3'}, {'callbackUri': 'http://127.0.0.1/subscribe', 'id': '0e46a74e-303b-11e9-a75b-fa163ec3fde3'}, {'callbackUri': 'https://127.0.0.1:8048/alarm_notifications', 'id': '0c270b24-303c-11e9-b638-fa163ec3fde3'}]` of type `array`. Value must be of type(s): `('object',)`"https://forge.etsi.org/rep/nfv/api-tests/-/issues/10Robot script is not allowing POST,PUT methods in SOL003/VNFLifecycleManagemen...2019-02-21T10:57:02ZjonnadaRobot script is not allowing POST,PUT methods in SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robotrequest':
- 'method':
- "Request was not one of the allowed request methods. Got `post`: Expected one of: `{'delete', 'get', 'patch'}`"
'request':
- 'method':
- "Request was not one of the allowed request methods...request':
- 'method':
- "Request was not one of the allowed request methods. Got `post`: Expected one of: `{'delete', 'get', 'patch'}`"
'request':
- 'method':
- "Request was not one of the allowed request methods. Got `put`: Expected one of: `{'delete', 'get', 'patch'}`"https://forge.etsi.org/rep/nfv/api-tests/-/issues/11Robot script is expecting 'Etag' in response body, where it is not specified ...2019-02-21T10:57:07ZjonnadaRobot script is expecting 'Etag' in response body, where it is not specified in the SOL003 spec in SOL003/VNFLifecylceManagement-API/IndividualVNFInstance.robotProperty 'Etag' does not exist in:
{
"Access-Control-Allow-Origin": "*",
"Access-Control-Allow-Headers": "Content-Type",
"Access-Control-Allow-Methods": "GET, POST, PUT, DELETE, OPTIONS",
"Access-Control-Request-Headers":...Property 'Etag' does not exist in:
{
"Access-Control-Allow-Origin": "*",
"Access-Control-Allow-Headers": "Content-Type",
"Access-Control-Allow-Methods": "GET, POST, PUT, DELETE, OPTIONS",
"Access-Control-Request-Headers": "X-Requested-With, accept, content-type",
"Content-Length": "1815",
"Content-Type": "application/json",
"Version": "1.1.0",
"Date": "Thu, 14 Feb 2019 11:09:21 GMT",
"Server": "PasteWSGIServer/0.5 Python/2.7.9"
}
16:44:35.917
FAIL
Expected property 'response headers Etag' was not found.https://forge.etsi.org/rep/nfv/api-tests/-/issues/12Robot script is expecting 200 where 201 is required as per SOL003 spec in SOL...2019-02-21T10:57:13ZjonnadaRobot script is expecting 200 where 201 is required as per SOL003 spec in SOL003/VNFLifecycleManagement-API/VNFInstances.robot201 is not one of [200]
Failed validating 'enum' in schema:
{'enum': [200], 'type': 'integer'}
201 is not one of [200]
Failed validating 'enum' in schema:
{'enum': [200], 'type': 'integer'}
https://forge.etsi.org/rep/nfv/api-tests/-/issues/13Cannot download mockserver from Github2019-02-28T14:23:32ZMichele CarignaniCannot download mockserver from GithubThe repository documented in the wiki seems closed.
Any other known references?
If yes, please update the wiki page accordingly.The repository documented in the wiki seems closed.
Any other known references?
If yes, please update the wiki page accordingly.https://forge.etsi.org/rep/nfv/api-tests/-/issues/14SOL002-VNFFaultManagement-API/Alarms.robot: Typo on ETag2019-03-11T10:33:29ZElian KrajaSOL002-VNFFaultManagement-API/Alarms.robot: Typo on ETagOn the tests, the tag is written Etag not ETag (T uppercase)
SOL002-VNFFaultManagement-API/Alarms.robot (check other files containing ETag)On the tests, the tag is written Etag not ETag (T uppercase)
SOL002-VNFFaultManagement-API/Alarms.robot (check other files containing ETag)Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/15SOL002-VNFFaultManagement-API/Alarms.robot: ETag missing on PATCH requests2019-03-11T10:38:57ZElian KrajaSOL002-VNFFaultManagement-API/Alarms.robot: ETag missing on PATCH requestsETag is missing on the PATCH requests where ETag is checked.
Need to be added.
Logic also need to be revised, in order to better handle the check.ETag is missing on the PATCH requests where ETag is checked.
Need to be added.
Logic also need to be revised, in order to better handle the check.Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/16SOL003-VNFLifeCycleManagement-API - IndividualVNFInstance.robot: Different vn...2019-03-11T10:39:11ZElian KrajaSOL003-VNFLifeCycleManagement-API - IndividualVNFInstance.robot: Different vnfInstanceId are neededIn order to execute the deletions in
- Delete VNF Instance - conflict an vnfInstanceId different from the one in ${vnfInstanceId} is needed. The vnfInstance shall be in INSTANTIATED state.
Test should have a new variable with a differe...In order to execute the deletions in
- Delete VNF Instance - conflict an vnfInstanceId different from the one in ${vnfInstanceId} is needed. The vnfInstance shall be in INSTANTIATED state.
Test should have a new variable with a different idElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/17SOL003-VNFLifeCycleManagement-API - Instantiate2019-03-11T10:39:31ZElian KrajaSOL003-VNFLifeCycleManagement-API - InstantiateIn order to execute instantiations, in
- Instantiate a vnfInstance Conflict task a different id should be used. The vnfInstanceId provided should refer to a vnf instance in INSTANTIATED state
Test must provide a new variable containin...In order to execute instantiations, in
- Instantiate a vnfInstance Conflict task a different id should be used. The vnfInstanceId provided should refer to a vnf instance in INSTANTIATED state
Test must provide a new variable containing the new valueElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/18SOL003-VNFLifeCycleManagement-API - Operate: Typo on json file2019-03-11T10:39:43ZElian KrajaSOL003-VNFLifeCycleManagement-API - Operate: Typo on json fileThe file operateVnfRequest.json on robot files has a typo. It is written operateVnFRequest.json (F uppercase)
Need to modify it on serveral test cases on the Operate test suiteThe file operateVnfRequest.json on robot files has a typo. It is written operateVnFRequest.json (F uppercase)
Need to modify it on serveral test cases on the Operate test suiteElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/19SOL003-VNFLifeCycleManagement-API - Operate: Logic revise on task Operate a v...2019-03-11T10:41:28ZElian KrajaSOL003-VNFLifeCycleManagement-API - Operate: Logic revise on task Operate a vnfInstance Conflict (parallel LCM operation)The task Operate a vnfInstance Conflict (parallel LCM operation) need to be executed just after the Operate a vnfInstance task.
A log time consuming operation may be required in order to make the test validated (scale, heal etc.)The task Operate a vnfInstance Conflict (parallel LCM operation) need to be executed just after the Operate a vnfInstance task.
A log time consuming operation may be required in order to make the test validated (scale, heal etc.)Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/20Duplicate subscriptions for notifications2021-06-03T08:49:18ZMichele CarignaniDuplicate subscriptions for notifications# Issue
Currently 2 tests are present to address the situations labelled `DUPLICATION` and `NOT-DUPLICATION`. Only one of the tests is run according to the value of the `VNF_DUPLICATION` variable.
This may lead to confusion.
# Proposal...# Issue
Currently 2 tests are present to address the situations labelled `DUPLICATION` and `NOT-DUPLICATION`. Only one of the tests is run according to the value of the `VNF_DUPLICATION` variable.
This may lead to confusion.
# Proposal
* [x] Rename the variable to a more meaningful name: `VNFM_ALLOWS_DUPLICATE_SUBS`
* [x] Merge the tests into one test (for each API) where an `If` keyword selects response code and body