aum-rollback-bootcount manual

critical

Image Types:
fixedfunction-armhf / fixedfunction-arm64 / fixedfunction-amd64
Image Deployment:
OSTree
Type:
functional

Description

Apertis update manager: Rollback bootcount This test ensures that the update manager is able to rollback to an old deployment in case of bootcount exceeded.

Pre Conditions

  1. Clone the tests repository from another computer (Note that the branch being tested may change depending on the release, please make sure to clone the correct branch for the release in question):
    2. $ git clone --branch apertis/v2025pre https://gitlab.apertis.org/tests/aum-offline-upgrade.git
  2. Copy the test directory aum-offline-upgrade to the target device:
    3. $ DUT_IP=<device-ip>
    $ scp -r aum-offline-upgrade user@$DUT_IP:
  3. Log into the target device:
    4. $ ssh user@$DUT_IP

Execution Steps

  1. # For Phase 1-3, perform the following actions to move to the next phase, the actions prepare the system and run the test in the appropriate phase
  2. Enter test directory
    3. $ cd aum-offline-upgrade
  3. Set environment variables
    4. $ source /etc/os-release
    $ ARCH=`dpkg --print-architecture`
  4. Set additional variables which will be use to generate the image file path base on the images available in the server, as example
    5. $ BASEURL="https://images.apertis.org" BOARD="uboot" IMGPATH="daily/$VERSION"
  5. Run the actual test
    6. $ common/run-test-in-systemd --timeout=1200 --name=rollback-bootcount env DEBUG=2 RELEASE=$VERSION ARCH=$ARCH BASEURL=$BASEURL IMGPATH=$IMGPATH IMGDATE=$BUILD_ID IMGTYPE=$VARIANT_ID BOARD=$BOARD ./run-test-ota-auto.sh
  6. Reboot the system
  7. For Phase 4, power cycle the board just after starting the kernel, repeat it for three times to increase bootcount beyond the limit
  8. Check that bootlimit has been exceeded, by looking at logs
  9. Check that after booting the original deployment has been used

Expected

If the test succeeds you will see a log entry

Warning: Bootlimit (3) exceeded. Using altbootcmd.

...

Found /extlinux/extlinux-rollback.conf

Retrieving file: /extlinux/extlinux-rollback.conf

Notes

  • Make sure to boot from the device configured for rollback, if not the bootcount will not be increased
  • The test uses internet
  • The test will prepare the system to perform an OTA update
  • It requires five phases, which require a manual reboot to complete
  • Phase 1 is to prepare the system with a version that can be updated
  • Phase 2 aims to clean the old deployment to allow the update
  • Phase 3 performs the OTA update
  • Phase 4 is to simulate a boot failure three times to exceed the bootcount
  • Phase 5 is to check that the system rollback to the previous state