Description | iDRAC firmware update through Redfish may fail an error message is displayed "400 BadRequest-InstanceID for operation is Invalid" while the system is under performance stress. |
Workaround | Retry the update operation. |
Systems Affected | All systems supported by this release |
Tracking number | 263709 |
Description | Running schema validator to check schema conformance may display an error about NetworkAttributeRegistry instance that the JSON does not match the required URIs in Schema of AttributeRegistry. |
Workaround | N/A |
Systems Affected | All systems supported by this release |
Tracking number | 268459 |
Description | GET method on the Ports collection URI with a filter query parameter that includes "ne" operator returns incorrect details. |
Workaround | N/A |
Systems Affected | All systems supported by this release |
Tracking number | 261094 |
Description | Expand query parameter may fail for a few resources while just GET method works as expected. |
Workaround | N/A |
Systems Affected | All systems supported by this release with external enclosures. |
Tracking number | 261043 |
Description | SmartNIC or DPU Secureboot certificates are not displaying in the response when GET is performed on Redfish certificate URI right after DPU/NIC was restarted. |
Workaround | N/A |
Systems Affected | All systems supported by this release |
Tracking number | 25844/257322 |
Description | After a chassis reset that is performed through Redfish, if the ResetType is set to PowerCycle, then system may power off and fail to power on automatically. |
Workaround | Power on the system using any iDRAC interface. |
Systems Affected | All systems supported by this release |
Tracking number | 234900 |
Description | While applying firmware update through Redfish interface for a device that does not require a reboot for the update, setting @Redfish.OperationApplyTime property to Immediate in the request body may cause the server to reboot. |
Workaround | N/A |
Systems Affected | All systems supported by this release |
Tracking number | 233764 |
Description | Redfish Life Cycle Events may report incorrect data for fan sensor URI after a hot pluggable fan is removed. |
Workaround | Restart the host system. |
Systems Affected | All systems supported by this release. |
Tracking number | 193777 |
Description | To continue support firmware backward compatible, you may get errors for Redfish API services in the Service Validator. They do not have any functional impact on the system and may be ignored. |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 183321 |
Description | Top query on a Parity URI instance returns complete response instead of an error code. |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 175801 |
Description | While performing GET method on BIOS or Manager Schema through Redfish, the SoftwareImages property may not display the uploaded firmware link. |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 156737 |
Description | If the partitions are disabled on FCoE capable CNA cards, few HII attributes values for WWN, VirtWWN, WWPN, VirtWWPN are displayed in the iDRAC GUI's Network page. However, the same data is not displayed when Get commands are performed in Redfish and RACADM interfaces. |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 151560 |
Description | Creating a recurring job will fail if the same job was completed recently and its Task ID still exists. |
Workaround | Wait for ten minutes for the Task ID to be deleted. |
Systems Affected | All systems supported by this release. |
Tracking number | 147501 |
Description | If you perform a Get operation for a PCIe device using Redfish API, the response may not display the model and serial number of the device. |
Workaround | N/A |
Systems Affected | All systems supported by this release. |
Tracking number | 111564 |