Investigate upstreamble solution for rollback support when using u-boot with bootstd
Affected images versions
Not relevant - Apertis specific solution found for RPi4 in #644 (closed), but not long term solution.
Unaffected images versions
Not relevant - Local fix implemented.
Testcase
- Boot Apertis on RPi4
- Check to see if it's using bootstd (bootflow)
- Perform steps to cause rollback and have it succeed
Steps to reproduce
- Boot Apertis on RPi4, note that it's currently using the distroboot mechanism.
- Perform steps required to cause rollback.
Expected result
- We boot using the bootstd/bootflow process (as the RPi boards have switched to this in upstream U-Boot).
- We have functioning rollback support.
Actual result
- We are either using distroboot support or rollback support is broken.
Reproducibility
How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?
Put the
-
✅ always - often, but not always
- rarely
Impact of bug
We are carrying local modifications that it's clear would not be acceptable upstream. Upstream U-Boot is moving towards bootstd as the preferred solution, so we should find a way to make rollback support work with it.
Attachments
Add further information about the environment in the form of attachments here. Attach plain text files from log output (from
journalctl,systemctl, …) or long backtraces as attached files. If adding comments on the log is required create a new snippet and add the link to it here.
Screenshots and videos are usually useful for graphic issues.
Root cause
Changes to preferred boot process in upstream U-Boot.
Outcomes
TBD
Management data
This section is for management only, it should be the last one in the description.
/cc @andrunko @em @Balasubramanian @sudarshan @wlozano
Phabricator link: https://phabricator.apertis.org/T10699