NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2021-03-18T05:14:42Zhttps://forge.etsi.org/rep/nfv/SOL006/-/issues/31Improving nsProfile attribute description and fix enum values2021-03-18T05:14:42ZppreeImproving nsProfile attribute description and fix enum valuesv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/30Add VirtualLinkProtocolData missing in VirtualLinkProfile based on IFA014ed3412021-03-18T05:14:55ZppreeAdd VirtualLinkProtocolData missing in VirtualLinkProfile based on IFA014ed341NFVIFA(19)000864r3_IFA014_-_VirtualLinkProtocolData_is_missing_in_VirtualLinkProfile
And also fixes enum values.NFVIFA(19)000864r3_IFA014_-_VirtualLinkProtocolData_is_missing_in_VirtualLinkProfile
And also fixes enum values.v3.5.1ppreeppreehttps://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/SOL006/-/issues/29Fix-IFA014ed341-IFA015_harmonization_corrections, set2 and addressing data in...2021-03-18T05:21:36ZppreeFix-IFA014ed341-IFA015_harmonization_corrections, set2 and addressing data inconsistencyNFVIFA(20)000276_IFA014ed341-IFA015_harmonization_corrections
NFVIFA(20)000290_IFA014ed341-IFA015_harmonization_corrections_set2
And fixes on addressing data inconsistencyNFVIFA(20)000276_IFA014ed341-IFA015_harmonization_corrections
NFVIFA(20)000290_IFA014ed341-IFA015_harmonization_corrections_set2
And fixes on addressing data inconsistencyv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/28Fix Enum Values and description from IFA011ed3412021-03-18T05:08:28ZppreeFix Enum Values and description from IFA011ed341v3.5.1ppreeppreehttps://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/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/SOL006/-/issues/27Adding Trunk port logical topology in VDU2021-03-18T05:06:58ZppreeAdding Trunk port logical topology in VDUv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/26Fix - IFA011ed341 based on 942 part1, part2 and part32021-03-17T04:12:04ZppreeFix - IFA011ed341 based on 942 part1, part2 and part3Covers corrections based on 3 CRs of IFA011ed341.Covers corrections based on 3 CRs of IFA011ed341.v3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/25FEAT02 add identifier ChangeCurrentVnfPackageOpConfig and fix cardinality2021-03-17T04:08:58ZppreeFEAT02 add identifier ChangeCurrentVnfPackageOpConfig and fix cardinalityv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/api-tests/-/issues/145GET APIs with Range request in v2.6.1 VNFPackageManagement-API2021-06-03T08:49:18ZyaoyuyGET APIs with Range request in v2.6.1 VNFPackageManagement-APIWhen do the test GET APIs with range request , the results turned failed because of the keywords 'Check HTTP Response Header Content-Range Is Present and Matches the requested range'.
In the code the Content-Range value in response shoul...When do the test GET APIs with range request , the results turned failed because of the keywords 'Check HTTP Response Header Content-Range Is Present and Matches the requested range'.
In the code the Content-Range value in response should be equal with the Range value in request.
But as far as i know, when the range value is added to request like "Range: bytes=0-1023", the actual size of the file will be added to the Content-Range value in response like "Content-Range: bytes=0-1023/2000".
So the value of these two values can't be equal.
We found this problem in VNFPackageContent and VNFPackageArtifacrs both in SOL003 AND SOL005https://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/SOL006/-/issues/24Add fixedIpAddress attribute to L3AddressData2021-03-16T14:34:58ZppreeAdd fixedIpAddress attribute to L3AddressDatav3.5.1ppreeppreehttps://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/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/141Robot keyword "Create Mock Http Forward" SOL003 VNFLifecycleManagement-API "...2021-01-27T20:22:12Zraducccradu@luxoft.comRobot keyword "Create Mock Http Forward" SOL003 VNFLifecycleManagement-API "2.6.1"After running robot HealVNFWorkflow.robot:
Error with the following message is triggered:
No keyword with name 'Create Mock Http Forward' found.
python library robotframework-mockserver has the following versions available:
from versi...After running robot HealVNFWorkflow.robot:
Error with the following message is triggered:
No keyword with name 'Create Mock Http Forward' found.
python library robotframework-mockserver has the following versions available:
from versions: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7
Same issue happens with:
No keyword with name 'Create Mock Expectation With Http Forward' found.
Should these keywords: "Create Mock Http Forward", "Create Mock Expectation With Http Forward" work within "robotframework-mockserver" library, or they are a mistake.https://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/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/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/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.json