'Verify Update' pop-up does not appear immediately after firmware flash completes

[huyle-anh]

Describe the bug:
The "Verify Update" pop-up only appears after the full 6-minute timer expires, regardless of whether the firmware flash process is already completed. This causes unnecessary delays in notifying the user about the completion of the firmware update.

Steps to reproduce the behavior:

1. Navigate to the WebUI page → Firmware → Start Update.
2. Observe that the "Verify Update" pop-up does not appear immediately after the firmware flash completes.
3. Wait for the 6-minute timer to expire.
   Notice that the pop-up only appears after the timer finishes.

Expected behavior

• The "Verify Update" pop-up should appear as soon as the firmware flash process is completed. The 6-minute timer should only be used as a fallback mechanism if the process takes longer than expected.

OS: MACOS Ventura - Version 13.7
Browser: Chrome
Version: 130.0.6723.116

[huyle-anh]

Any comments on this?
My solution is to check the status of TaskState via /redfish/v1/TaskService/Tasks, and if it is "Complete", a popup "Verify Update".

[mdmillerii]

I thought I had replied but there were two similar issues opened.

As stated elsewhere they current code BMC code update manager does not rember it was in progress across the reboot phase.[1] It just becomes unresponsive for a while then is suddenly running the new version.

If the GUI tries to check during this time it might encounter TCP timeouts causing even longer delays as exponential back off in network traffic eventually detecting a failure minutes after the BMC is again available.

The 6 minute delay has not been turned to any platform. The time to erase and write the flash can vary significantly. I know one earlier platform was taking over 20 minutes when capacity was 1/4 or 1/8 the current size.

[1] Elsewhere (probably in discord) I discussed a possible route of exploration to remember, but the feature wasn't part of the design considerations and the proposed scheme to remember might the route only be available for chance. Or it will take significant design to work. I will not have time to explore this in foreseeable Future (beyond coaching an experienced C++ OpenBMC programmer who wants to explore).