NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2021-03-17T04:08:58Zhttps://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/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/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.jsonhttps://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/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/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/SOL005/-/issues/17Incorrect SOL005/VNFPackageManagement/PkgmNotificationFilter schema2021-09-28T14:56:39ZSana ZulfiqarIncorrect SOL005/VNFPackageManagement/PkgmNotificationFilter schemaThe file: https://forge.etsi.org/rep/nfv/SOL005/blob/2.7.1-dev/src/SOL005/VNFPackageManagement/definitions/SOL005VNFPackageManagement_def.yaml
The Schema of "PkgmNotificationsFilter" is incorrect. According to the SOL005 specification, ...The file: https://forge.etsi.org/rep/nfv/SOL005/blob/2.7.1-dev/src/SOL005/VNFPackageManagement/definitions/SOL005VNFPackageManagement_def.yaml
The Schema of "PkgmNotificationsFilter" is incorrect. According to the SOL005 specification, Attributes vnfdId, vnfPkgId, operationalState, usageState, vnfmInfo are part of "PkgmNotificationsFilter" instead of "vnfProductsFromProviders".
The current implementation is like this:
![SOL005-pkgm](/uploads/c65ed4fe3f4c1f6e87dfed5cfe2d28da/SOL005-pkgm.PNG)
Implementation should be like that (reference v2.7.1/SOL005-9.5.3.4):
![image](/uploads/4033698f34919ad4d9e1516a334f276e/image.png)Sana ZulfiqarSana Zulfiqarhttps://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/SOL005/-/issues/16NsLocationConstraint data type.2021-01-13T18:08:17ZVlademir BrusseNsLocationConstraint data type.The InstantiateNsRequest data type has the nestedNslocationConstraints attribute defined as items: $ref: "#/definitions/NsLocationConstraint".
NsLocationConstraint does not exist in SOL005 v3.3.1 and should be replaced with NestedNsloc...The InstantiateNsRequest data type has the nestedNslocationConstraints attribute defined as items: $ref: "#/definitions/NsLocationConstraint".
NsLocationConstraint does not exist in SOL005 v3.3.1 and should be replaced with NestedNslocationConstrainsts and the definition of the NsLocationConstraint data type (line 4921) removed.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/15nsCpHandle attribute.2021-01-19T14:23:05ZVlademir BrussensCpHandle attribute.The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of t...The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of the SOL005 v2.4.1), because the cardinality 0..1 means that attribute is Optional and not an Array.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/14nsCpHandle attribute.2021-01-19T14:20:59ZVlademir BrussensCpHandle attribute.The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of t...The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of the SOL005 v2.5.1), because the cardinality 0..1 means that attribute is Optional and not an Array.
The NfpInfo data type also has the cpGroup attribute defined as items: $ref: "#/definitions/NsCpHandle" that should be items: $ref: "#/definitions/CpGroupInfo" as defined for NfpData.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/13nsCpHandle attribute.2021-01-13T18:09:09ZVlademir BrussensCpHandle attribute.The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of t...The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of the SOL005 v2.6.1), because the cardinality 0..1 means that attribute is Optional and not an Array.
The NfpInfo data type also has the cpGroup attribute defined as items: $ref: "#/definitions/NsCpHandle" that should be items: $ref: "#/definitions/CpGroupInfo" as defined for NfpData.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/12nsCpHandle attribute.2021-09-28T14:56:39ZVlademir BrussensCpHandle attribute.The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of t...The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of the SOL005 v2.7.1), because the cardinality 0..1 means that attribute is Optional and not an Array.
The NfpInfo data type also has the cpGroup attribute defined as items: $ref: "#/definitions/NsCpHandle" that should be items: $ref: "#/definitions/CpGroupInfo" as defined for NfpData.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/11nsCpHandle attribute.2021-09-28T14:56:39ZVlademir BrussensCpHandle attribute.The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of t...The nsCpHandle attribute with cardinality 0..1 in NsLinkPortInfo and VnffgInfo data types should have the yaml code generated as type “object” and not type “array” (as it is generated in the SOL005NSLifecycleManagement_def.yaml file of the SOL005 v3.3.1), because the cardinality 0..1 means that attribute is Optional and not an Array.
The NfpInfo data type also has the cpGroup attribute defined as items: $ref: "#/definitions/NsCpHandle" that should be items: $ref: "#/definitions/CpGroupInfo" as defined for NfpData.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/10Swagger File: VNFPackageManagement.yaml; Get '/vnf_packages' should not have ...2021-01-19T12:05:55ZjaissSwagger File: VNFPackageManagement.yaml; Get '/vnf_packages' should not have property 'VnfPkgInfo'The file:
https://forge.etsi.org/rep/nfv/SOL005/blob/v2.7.1/src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml
Get '/vnf_packages' has following response:
```yaml
schema:
type: array
items:
...The file:
https://forge.etsi.org/rep/nfv/SOL005/blob/v2.7.1/src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml
Get '/vnf_packages' has following response:
```yaml
schema:
type: array
items:
properties:
VnfPkgInfo:
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfo"
```
whereas its should be
```yaml
schema:
type: array
items:
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfo"
```
property 'VnfPkgInfo' is not required. Its a Data Type and not property.
Reference: Attached screenshot from 2.7.1 SOL005 Spec.
![Screen_Shot_2020-12-16_at_12.44.19_PM](/uploads/bdfb142a57c5a0c24a500452345cd293/Screen_Shot_2020-12-16_at_12.44.19_PM.png)