-
Bug
-
Resolution: Done
-
Medium
-
Istanbul Release
Sending attached json file with VES event results in the following error (VES Collector log):
StndDefinedSchemaValidator.thresholdInfo.observedValue: More than 1 schema is valid. (code: 1023) From: StndDefinedSchemaValidator.</opt/app/VESCollector/./etc/externalRepo/3gpp/rep/sa5/MnS/blob/Rel16/OpenAPI/faultMnS.yaml#/components/schemas/NotifyNewAlarm>.<allOf>.thresholdInfo.<#/components/schemas/ThresholdInfo>.observedValue.<oneOf>
This scenario requires exactly the same steps to recreate as DCAEGEN2-2893 with the following changed applied to the yaml file:
# provMnS.yaml remove following lines: 417,419d416 < - $ref: 'nrNrm.yaml#/components/schemas/resources-nrNrm' < - $ref: '5gcNrm.yaml#/components/schemas/resources-5gcNrm' < - $ref: 'sliceNrm.yaml#/components/schemas/resources-sliceNrm'
In fact schema 'ThresholdInfo' is defined in both files:
- faultMnS.yaml
- genericNrm.yaml
it's completely different object and as long as the same schema name is used in two different files, it's valid reference. In this case however validator can't determine proper one regardless the fact, that ref in the faultMnS.yaml points to the same file:
$ref: '#/components/schemas/ThresholdInfo'
- relates to
-
DCAEGEN2-2895 VES Collector stndDefinedFields schema validation reference overkill
- Closed
-
DCAEGEN2-2893 VES Collector stndDefinedFields schema validation issue
- Closed