NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2022-05-10T04:46:25Zhttps://forge.etsi.org/rep/nfv/SOL006/-/issues/48IFA011ed361-Add standardized interface requirements to VirtualNetworkInterfac...2022-05-10T04:46:25ZppreeIFA011ed361-Add standardized interface requirements to VirtualNetworkInterfaceRequirementsv3.6.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/49IFA011ed361_FEAT03 Add missing minNumberofPreservedInstances attribute to Nfv...2022-05-10T04:46:11ZppreeIFA011ed361_FEAT03 Add missing minNumberofPreservedInstances attribute to NfviMaintenanceInfo IEv3.6.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/47IFA011ed361 Adding externallyManaged attribute to VnfVirtualLinkDesc2022-05-10T04:45:13ZppreeIFA011ed361 Adding externallyManaged attribute to VnfVirtualLinkDescv3.6.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/46IFA011ed361_Fixing IpAddressAssignment flag2022-05-10T04:44:52ZppreeIFA011ed361_Fixing IpAddressAssignment flagv3.6.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL009/-/issues/3OpenAPI wiki page - NFVManoConfigurationAndInformationManagement-API of v3.5....2022-01-31T11:10:58ZVlademir BrusseOpenAPI wiki page - NFVManoConfigurationAndInformationManagement-API of v3.5.1 showing several errors on "Editor" page.In the "NFVManoConfigurationAndInformationManagement-API" of SOL009 v3.5.1 it is showing several errors when rendering the swagger "Editor" page on Chrome browser.
The use of "oneOf" should be investigated here since in v3.3.1 does not ...In the "NFVManoConfigurationAndInformationManagement-API" of SOL009 v3.5.1 it is showing several errors when rendering the swagger "Editor" page on Chrome browser.
The use of "oneOf" should be investigated here since in v3.3.1 does not have this issue. If so, we need a solution for that.
Structural error at paths./peer_entities.post.requestBody
should have required property '$ref'
missingProperty: $ref
Jump to line 18171
Structural error at paths./peer_entities.post.requestBody
should match exactly one schema in oneOf
Jump to line 18171
...
Giacomo answered that "this is because some data types inside this API have "type" as attribute names, which is also an OpenAPI keyword. So it is a kind of warning that the editor page tool gives to signal it. Not sure how to be avoided to be honest, as we cannot change the attribute name "type" otherwise it will not be compliant with SOL specs."Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/21Query params should not be defined as global parameters in SOL005_params.yaml2022-01-31T08:24:12ZVlademir BrusseQuery params should not be defined as global parameters in SOL005_params.yamlSOL005 is using the same parameters in the file SOL005_params.yaml of the GET methods for all interfaces including "NS Lifecycle Management" and "NS Performance Management" interfaces, for example, but the parameters for both are differe...SOL005 is using the same parameters in the file SOL005_params.yaml of the GET methods for all interfaces including "NS Lifecycle Management" and "NS Performance Management" interfaces, for example, but the parameters for both are different and can be different for others.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL005_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL002-SOL003/-/issues/3Query params should not be defined as global parameters in SOL002SOL003_param...2022-01-25T10:10:17ZVlademir BrusseQuery params should not be defined as global parameters in SOL002SOL003_params.yaml.SOL002 and SOL003 are using the same parameters in the file SOL002SOL003_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open po...SOL002 and SOL003 are using the same parameters in the file SOL002SOL003_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL002SOL003_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL009/-/issues/4Query params should not be defined as global parameters in SOL009_params.yaml.2022-01-19T11:54:19ZVlademir BrusseQuery params should not be defined as global parameters in SOL009_params.yaml.SOL009 is using the same parameters in the file SOL009_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the u...SOL009 is using the same parameters in the file SOL009_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL009_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/45IFA011ed361_removal of deprecated element in vnf.2021-12-13T07:41:18ZppreeIFA011ed361_removal of deprecated element in vnf.delete supportMandatory attribute marked deprecated in v3.3.1 from VirtualNetworkInterfaceRequirements information elementdelete supportMandatory attribute marked deprecated in v3.3.1 from VirtualNetworkInterfaceRequirements information elementv3.6.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/39IFA011ed351_segmentationType definition to subport level.2021-10-28T05:16:41ZppreeIFA011ed351_segmentationType definition to subport level.Follows NFVIFA(20)000387r1: IFA011ed351_Fix_Typos in clause 7-1-6 sync_to_IFA015_work
to correct segmentationType definition to subport level.Follows NFVIFA(20)000387r1: IFA011ed351_Fix_Typos in clause 7-1-6 sync_to_IFA015_work
to correct segmentationType definition to subport level.v3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/38IFA014ed351_Dependencies IE description improvement2021-10-28T05:16:04ZppreeIFA014ed351_Dependencies IE description improvementNFVIFA(20)000480r2_IFA014ed351_Dependencies_IE_description_improvementNFVIFA(20)000480r2_IFA014ed351_Dependencies_IE_description_improvementv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/40IFA011ed351 Add missing Dependencies IE definition2021-10-28T05:14:51ZppreeIFA011ed351 Add missing Dependencies IE definitionNFVIFA(20)000482r1: IFA011ed351 Add missing Dependencies IE definitionNFVIFA(20)000482r1: IFA011ed351 Add missing Dependencies IE definitionv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/41IFA011ed351 updates related to the use of VIPs2021-10-28T05:14:28ZppreeIFA011ed351 updates related to the use of VIPsFollows NFVIFA(20)000599r1
for changes VipCpd:
reference to intVirtualLinkDesc and a flag “dedicatedIPAddress” added.
reference to VnfExtCp attribute removed
And a additional fix in referencing vdu-cpdFollows NFVIFA(20)000599r1
for changes VipCpd:
reference to intVirtualLinkDesc and a flag “dedicatedIPAddress” added.
reference to VnfExtCp attribute removed
And a additional fix in referencing vdu-cpdv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/43IFA011ed351 updates scaling descriptors related to use of VIPs2021-10-28T05:14:00ZppreeIFA011ed351 updates scaling descriptors related to use of VIPsFollows NFVIFA(20)000614r7: IFA011ed351 updates of scaling descriptors related to the use of VIPsFollows NFVIFA(20)000614r7: IFA011ed351 updates of scaling descriptors related to the use of VIPsv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/34VnfLcmOperation coordination based on IFA011ed3512021-10-28T05:13:11ZppreeVnfLcmOperation coordination based on IFA011ed351Changes implemented from IFA011ed351 Cross stages alignment w.r.t. LCM coordinationChanges implemented from IFA011ed351 Cross stages alignment w.r.t. LCM coordinationv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/api-tests/-/issues/195Bad use of Format String when replacing value of callbackUri attribute2021-10-08T23:32:22ZGiacomo BerniniBad use of Format String when replacing value of callbackUri attributeShould be replaced with Replaced String as we do not use templating in v2.4.1Should be replaced with Replaced String as we do not use templating in v2.4.1Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/api-tests/-/issues/194Keywords not running when testing Individual VNFInstances SOL003 VNFLifecycle...2021-10-08T01:33:04ZyaoyuyKeywords not running when testing Individual VNFInstances SOL003 VNFLifecycleMangementAPI V2.6.1when testing task PATCH Individual VNFInstance Precondition failed and PATCH Individual VNFInstance Conflict
the keywords Launch another LCM operation and SET etag should run, but in the log file, It seems not runnningwhen testing task PATCH Individual VNFInstance Precondition failed and PATCH Individual VNFInstance Conflict
the keywords Launch another LCM operation and SET etag should run, but in the log file, It seems not runnninghttps://forge.etsi.org/rep/nfv/api-tests/-/issues/190Wrong Problem Details JSON Object set in Keywords Check HTTP Response Body Js...2021-10-05T10:15:18ZyaoyuyWrong Problem Details JSON Object set in Keywords Check HTTP Response Body Json Schema Is ProblemDetails SOL005 VNFPackageManagementAPI v2.6.1When check HTTP Response Body Json Schema Is ProblemDetails
the problem details json object should be application/problem+json according to the RFC7807
but now the value is application/json
https://datatracker.ietf.org/doc/html/rfc7807When check HTTP Response Body Json Schema Is ProblemDetails
the problem details json object should be application/problem+json according to the RFC7807
but now the value is application/json
https://datatracker.ietf.org/doc/html/rfc7807https://forge.etsi.org/rep/nfv/api-tests/-/issues/193unexpected GET method runs after http code 303 returned in Subscriptions.robo...2021-10-05T10:15:18Zyaoyuyunexpected GET method runs after http code 303 returned in Subscriptions.robot SOL003 VNFLifecycleManagementAPIWhen testing Create a new Subscription - NO-DUPLICATION task,
robot runs GET API after getting 303 in header, and the response value now is from the GET API which cause the task failed.When testing Create a new Subscription - NO-DUPLICATION task,
robot runs GET API after getting 303 in header, and the response value now is from the GET API which cause the task failed.https://forge.etsi.org/rep/nfv/api-tests/-/issues/191[2.7.1] Test NSFaultManagement-API.Alarms Incorrect Schema validation.2021-10-05T10:15:18Zbanerjeesu[2.7.1] Test NSFaultManagement-API.Alarms Incorrect Schema validation.The plugtest validates faultDetails as type 'String'. However, as per the SOL005 2.7.1 spec, the type should be an array-of-string. The screenshot attached depicts the cardinality to be "0..N".
Rest Invocation (Plugtest logs)
---
<pre>
...The plugtest validates faultDetails as type 'String'. However, as per the SOL005 2.7.1 spec, the type should be an array-of-string. The screenshot attached depicts the cardinality to be "0..N".
Rest Invocation (Plugtest logs)
---
<pre>
13:32:10.314 DEBUG "GET /telco/api/nsfm/v2/alarms HTTP/1.1" 200 None
13:32:10.317 TRACE Return: {'body': [{'_links': {'self': {'href': '/telco/api/nsfm/v2/alarms/a761571b-91b8-478e-946c-7b3497eabb65'}},
'ackState': 'UNACKNOWLEDGED',
'alarmRaisedTime': 'Sat Jul 24 00:16:49 GMT 2021',
'eventTime': 'Sat Jul 24 00:17:58 GMT 2021',
'eventType': 'PROCESSING_ERROR_ALARM',
'faultDetails': ['Cannot find vnfInstance Name for vnfInstanceId:"803d3a8c-9957-4c33-8fba-a13c729c0c5b" of an alarm with id:"a761571b-91b8-478e-946c-7b3497eabb65"'],
'faultType': 'Failed to create number of replica(s) after specified number of tries',
'id': 'a761571b-91b8-478e-946c-7b3497eabb65',
'isRootCause': True,
'managedObjectId': '803d3a8c-9957-4c33-8fba-a13c729c0c5b',
'perceivedSeverity': 'WARNING',
'probableCause': 'ProgressDeadlineExceeded'},
{'_links': {'self': {'href': '/telco/api/nsfm/v2/alarms/b85dba2e-978c-4d11-94dd-642b4270c719'}},
'ackState': 'UNACKNOWLEDGED',
'alarmRaisedTime': 'Sat Jul 24 01:22:35 GMT 2021',
'eventTime': 'Sat Jul 24 01:22:59 GMT 2021',
'eventType': 'PROCESSING_ERROR_ALARM',
'faultDetails': ['Cannot find vnfInstance Name for vnfInstanceId:"1ad2ee08-50d7-4a96-8288-9c1811467c91" of an alarm with id:"b85dba2e-978c-4d11-94dd-642b4270c719"'],
'faultType': 'Failed to create number of replica(s) after specified number of tries',
'id': 'b85dba2e-978c-4d11-94dd-642b4270c719',
'isRootCause': True,
'managedObjectId': '1ad2ee08-50d7-4a96-8288-9c1811467c91',
'perceivedSeverity': 'WARNING',
'probableCause': 'ProgressDeadlineExceeded'},
{'_links': {'self': {'href': '/telco/api/nsfm/v2/alarms/83e7ed6f-ccd1-4198-a102-55fee45fe7f7'}},
'ackState': 'ACKNOWLEDGED',
'alarmRaisedTime': 'Sat Jul 24 04:12:31 GMT 2021',
'eventTime': 'Sat Jul 24 04:13:00 GMT 2021',
'eventType': 'PROCESSING_ERROR_ALARM',
'faultDetails': ['Cannot find vnfInstance Name for vnfInstanceId:"383f176d-f592-4b49-88dd-3ac69edb3587" of an alarm with id:"83e7ed6f-ccd1-4198-a102-55fee45fe7f7"'],
'faultType': 'Failed to create number of replica(s) after specified number of tries',
'id': '83e7ed6f-ccd1-4198-a102-55fee45fe7f7',
'isRootCause': True,
'managedObjectId': '383f176d-f592-4b49-88dd-3ac69edb3587',
'perceivedSeverity': 'WARNING',
'probableCause': 'ProgressDeadlineExceeded'},
{'_links': {'self': {'href': '/telco/api/nsfm/v2/alarms/109d8d61-7e60-45ff-a3f7-506087fb2ad6'}},
'ackState': 'UNACKNOWLEDGED',
'alarmRaisedTime': 'Sat Jul 24 04:02:27 GMT 2021',
'eventTime': 'Mon Jul 26 18:12:31 GMT 2021',
'eventType': 'PROCESSING_ERROR_ALARM',
'faultDetails': ['Cannot find vnfInstance Name for vnfInstanceId:"383f176d-f592-4b49-88dd-3ac69edb3587" of an alarm with id:"109d8d61-7e60-45ff-a3f7-506087fb2ad6"'],
'faultType': 'Failed to pull image from docker repository',
'id': '109d8d61-7e60-45ff-a3f7-506087fb2ad6',
'isRootCause': True,
'managedObjectId': '383f176d-f592-4b49-88dd-3ac69edb3587',
'perceivedSeverity': 'CRITICAL',
'probableCause': 'ErrImagePull'}],
'headers': {'Cache-Control': 'no-cache, no-store, max-age=0, must-revalidate',
'Connection': 'Keep-Alive',
'Content-Encoding': 'gzip',
'Content-Type': 'application/json',
'Date': 'Thu, 23 Sep 2021 08:02:09 GMT',
'Expires': '0',
'Keep-Alive': 'timeout=5, max=100',
'Pragma': 'no-cache',
'Server': 'Apache',
'Set-Cookie': 'SESSION=c83359a4-9afd-464d-9833-bab15d0f1d4b; Path=/; Secure; HttpOnly',
'Strict-Transport-Security': 'max-age=31536000 ; includeSubDomains',
'Transfer-Encoding': 'chunked',
'Version': '2.7.1',
'X-Content-Type-Options': 'nosniff',
'X-Frame-Options': 'SAMEORIGIN',
'X-XSS-Protection': '1; mode=block',
'vary': 'accept-encoding',
'x-transaction-id': 'efdf095a-b6e5-41a6-9831-9849da30a2c5'},
'seconds': 0.20025800000000002,
'status': 200}
</pre>
Test Logs:
---
<pre>
13:32:10.342 FAIL ValidationError: Validation error for schema alarms.schema.json: ['Cannot find vnfInstance Name for vnfInstanceId:"803d3a8c-9957-4c33-8fba-a13c729c0c5b" of an alarm with id:"a761571b-91b8-478e-946c-7b3497eabb65"'] is not of type 'string'
</pre>
SOL Spec Screenshot
---
![Screenshot_2021-09-24_at_10.24.05_AM](/uploads/fa3378fc274849e2397555e3fa563a1b/Screenshot_2021-09-24_at_10.24.05_AM.png)