OS Update Failure Not Displayed in UI

[petermcd]

Describe the bug
I have attempted to build the BMC on my Mac and upload it to my Turing Pi. The build seemed successful but when I tried to update the Turing Pi using the OTA method the progress bar remains green and displays the message "Verifying checksum and finalizing upgrade..."

When looking at the browsers developer tools it is in fact receiving the following response continuously:

{
    "Error": "failed os_update (exit status: 255)"
}

To Reproduce
Steps to reproduce the behaviour:

Build custom OS using instructions for Mac
Use BMC UI to upload

Expected behavior
Upgrade to be successful or to output the failure message

Screenshots
If applicable, add screenshots to help explain your problem.

Versions
linux version=Linux turing-master-2 5.4.61 #1 SMP PREEMPT Tue Nov 28 13:52:46 UTC 2023 armv7l GNU/Linux
bmc version=Daemon version: 2.0.5
Build time: 2023-11-28 14:01:07-00:00
Build version: 2023.08
Buildroot release:
Buildroot 2023.08
API version: 1.1
BMC UI: v1.0.3

Additional context

Although I have built the firmware using the instructions in README.md there is every possibility there is something wrong, this should not however cause the WEB UI not to react to the failure received.

[petermcd]

Apologies. Created in the wrong repo, Recreated in the UI repo turing-machines/BMC-UI#19

[petermcd]

Reopening as this is a failure in the BMC rather than the GUI. The failure being reported to the UI has a http status code of 200 therefore the UI is not detecting it as an error.

The following is the summary of the headers for the failure response:

Summary
URL: https://192.168.1.175/api/bmc?opt=get&type=firmware
Status: 200
Source: Network
Address: 192.168.1.175:443
Initiator: 
app.js:2:85593

[petermcd]

Upon further investigation, this was user error. In the event anyone comes across this and has the same, the likely reason this occurred is due to missing the final step when flashing the firmware from the SD Card.

If you do not remove the SD Card it will continue to boot from the card rather than the onboard memory. If you take the card out and reboot it will likely work.