You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 2.4.8 version of the Redfish Validator does not find an error in the path DataSourceUri property of a FanSpeedsPercent collection in EnvironmentMetrics. The validator does not visit the DataSourceUri path during the validation.
The validator reports success even though 404 is returned for the DataSourceUri.
Following are excerpts from the log file showing the issue:
Example showing error with DataSourceUri that is not found by validator:
$ curl -k -H "X-Auth-Token: $token" https://${bmc}/redfish/v1/Chassis/chassis/Sensors/fan0_0
{
"@odata.id": "/redfish/v1/Chassis/chassis/Sensors/fan0_0",
"error": {
"@Message.ExtendedInfo": [
{
"@odata.type": "#Message.v1_1_1.Message",
"Message": "The requested resource of type fan0_0 named 'Sensor' was not found.",
"MessageArgs": [
"fan0_0",
"Sensor"
],
"MessageId": "Base.1.18.1.ResourceNotFound",
"MessageSeverity": "Critical",
"Resolution": "Provide a valid resource identifier and resubmit the request."
}
],
"code": "Base.1.18.1.ResourceNotFound",
"message": "The requested resource of type fan0_0 named 'Sensor' was not found."
}
}
I also ran the validator with --uricheck and no problems were reported for the DataSourceUri in that case either.
The text was updated successfully, but these errors were encountered:
It's possible the tool isn't stepping into DataSourceUri since it's not a typical reference link (with @odata.id), so it may just be performing basic string validation.
If this is the case, I think we should add a check specifically for DataSourceUri in the similar manner we added one for "Uri" in MessageRegistryFile to inspect the referenced registry.
The 2.4.8 version of the Redfish Validator does not find an error in the path DataSourceUri property of a FanSpeedsPercent collection in EnvironmentMetrics. The validator does not visit the DataSourceUri path during the validation.
The validator reports success even though 404 is returned for the DataSourceUri.
Following are excerpts from the log file showing the issue:
Example showing error with DataSourceUri that is not found by validator:
I also ran the validator with
--uricheck
and no problems were reported for the DataSourceUri in that case either.The text was updated successfully, but these errors were encountered: