Bug Fixes in This Version

4976718

Description: If a BMC task such as a log dump is started after the BMC firmware update task has been initiated but before monitoring has attached to it, the monitoring logic may track the other task instead of the firmware update task, which can cause the BMC reboot to fail.

Reported in version: 25.10-LTSU2

4917779

Description: Initiating an Arm GracefulReset can cause the BMC's Redfish UpdateService to incorrectly report its state as UnavailableOffline.

Reported in version: 25.10-LTSU2

4944048

Description: When upgrading or downgrading between the 25.10-LTSU2 and 26.04 releases, repeated BMC reboots may, in rare cases, cause the profile-manager service to fail due to a malformed JSON file. This failure triggers a core dump of the service, populates core dump logs, and causes the golden-image service to become unresponsive.

Reported in version: 25.10-LTSU2

5096810

Description: The Processor.Reset Redfish action incorrectly requires only the Login privilege for POST requests to /redfish/v1/Systems/<str>/Processors/<str>/Actions/Processor.Reset. This action should require the ConfigureComponents privilege per the Redfish privilege registry, as the Login privilege is granted to all authenticated users, including those in the ReadOnly role.

Reported in version: 25.10-LTSU2

5071650

Description: In rare cases, the EROT version string may contain space characters instead of the actual version characters, making the version appear partial. Rebooting the BMC reloads the string correctly.

Reported in version: 25.10-LTSU2

5017603

Description: During BFB installations via Redfish, the task state may change to "Exception" before the specific error message is appended to the HTTP response payload. This results in incomplete error logs on the initial poll following a failure.

Reported in version: 25.10-LTSU2

4994932

Description: In rare cases, the PLDM firmware update process in NIC mode may fail during the activation phase due to a transient communication error on the device.

Reported in version: 25.10-LTSU2

4966479

Description: In rare cases, accessing the /redfish/v1/Managers/Bluefield_BMC endpoint may time out due to repeated IPMB communication failures, causing the endpoint to become unresponsive. Resetting EFI variables and power cycling the system resolves the issue.

Reported in version: 25.10-LTSU2

5071627

Description: On some Aztlan BlueField-2 cards, the BMC may report false VCORE and 3P3V_AUX voltage warnings during normal operation. These false-positive warnings could appear in the system event log (SEL) and as warning sensor health in Redfish and IPMItool, triggering unnecessary alerts without indicating an actual hardware fault. This issue was fixed by adjusting the warning thresholds for the VCORE and 3P3V_AUX sensors to align with normal operating ranges.

Reported in version: 25.10-LTSU2

5071048

Description: Enhanced the Arm-side port link status reporting to ensure accurate link status evaluations and prevent false configuration error alarms in the BMC SEL log during DPU OS reboots.

Reported in version: 25.10-LTSU2

5071040

Description: Following a DPU reset, the BaseMAC, BaseGUID, and Description fields may incorrectly return as empty within the redfish/v1/Systems/Bluefield/Oem/Nvidia schema response.

Reported in version: 25.10-LTSU2

5030888

Description: When running OobUpdate --show_all_version repeatedly, the BOARD and/or BSP fields may intermittently return empty values due to a parsing issue in the OobUpdate script. The underlying firmware data remains available on the device.

Reported in version: 25.10-LTSU2

5030870

Description: Following a firmware update via the OobUpdate script, the version reported for components such as UEFI may occasionally fail to reflect the newly installed version. This is a transient reading error, not an update failure.

Reported in version: 25.10-LTSU2

5030860

Description: In rare cases, after a firmware upgrade, doca-installer --show-running-fw may report N/A for the CEC version on a device. The actual firmware is correctly installed; this is a transient read failure.

Reported in version: 25.10-LTSU2

5017581

Description: When performing a BMC firmware update via update-multipart with an incorrect target, the TaskStatus field may intermittently return OK instead of Critical, even when the update fails due to no matching devices.

Reported in version: 25.10-LTSU2

4970600

Description: Accumulated CPER (Common Platform Error Records) logs in /var/cper can fill the BMC root partition, causing critical BMC services such as entity-manager to fail. This can result in SDR read errors and ipmitool sdr elist failures.

Reported in version: 25.10-LTSU2

4966467

Description: Event log warnings for PLDM_Sensor_1_100 may appear in the BMC event log when the NIC temperature exceeds 91°C. These warnings are benign and will be removed in a future release.

Reported in version: 25.10-LTSU2

4935831

Description: After deleting an entry in the BMC WebUI Event Log, the table may not immediately reflect the deletion. Reloading the page displays the correct updated log.

Reported in version: 25.10-LTSU2

4885311

Description: In rare cases (approximately 1%), BMC sensors and SDR data may not be available within 2 minutes of a BMC reboot, due to additional initialization tasks introduced in recent versions.

Reported in version: 25.10-LTSU2