Post by tonyy on Nov 28, 2023 4:39:49 GMT
Hi there,
According to the definition of CPER in LogEntry, there are three properties here(Oem, NotificationType and SectionType).
When I tried to add the CPER in LogEntry like the following case, the redfish validator would report errors(This complex object Tonyy should be a dictionary or None, but it's of type str...).
The rest properties failed to check.
After changing the format to dictionary like this, the redfish validator still reported errors (This object's type Oem should be a Collection, but it's of type Resource.Oem...)
The rest properties still could be checked
As far as I know, Oem property should be an object defined in DSP2046 instead of array.
Do I miss something here? Could anyone help me to clarify it? thanks.
According to the definition of CPER in LogEntry, there are three properties here(Oem, NotificationType and SectionType).
When I tried to add the CPER in LogEntry like the following case, the redfish validator would report errors(This complex object Tonyy should be a dictionary or None, but it's of type str...).
The rest properties failed to check.
"CPER": {
"Oem": {
"Tonyy": "1234"
}
}
After changing the format to dictionary like this, the redfish validator still reported errors (This object's type Oem should be a Collection, but it's of type Resource.Oem...)
The rest properties still could be checked
"CPER": {
"Oem": [
[
"Tonyy"
]
]
}
As far as I know, Oem property should be an object defined in DSP2046 instead of array.
Do I miss something here? Could anyone help me to clarify it? thanks.
