apertis-update-manager-ota-api manual

medium

Image Types:
minimal-armhf
Image Deployment:
OSTree
Type:
functional

Description

Test the apertis-update-manager API for updates over the air.

Resources

  • The DUT u-boot environment must be clean: in u-boot, run: `env default -a` followed by `saveenv`
  • A PC must be connected to DUT serial port
  • The DUT must be connected to network

Execution Steps

  1. Check the initial deployment
    2. $ sudo ostree admin status
  2. Prepare the copy of commit and deploy to allow the upgrade to the same version
  3. Command below shows you an initial commit ID, for instance
    4. $ export BOOTID=$(sudo ostree admin status | sed -n -e 's/^\* apertis \([0-9a-f]*\)\.[0-9]$/\1/p'); echo $BOOTID
  4. Get the Collection ID and ref
    5. $ export CID=$(sudo ostree refs -c | head -n 1 | tr -d '(),' | cut -f 1 -d ' '); echo COLLECTION_ID=$CID
    $ export REF=$(sudo ostree refs -c | head -n 1 | tr -d '(),' | cut -f 2 -d ' '); echo REF=$REF
  5. Create the commit with changed timestamp to allow upgrade with recent update file
    6. $ export NEWID=$(sudo ostree commit --orphan --tree=ref=$BOOTID --add-metadata-string=ostree.collection-binding=$CID --bind-ref=$REF --timestamp="1 year ago"); echo "New commit: $NEWID"
  6. Deploy the prepared commit
    7. $ sudo ostree admin upgrade --allow-downgrade --deploy-only --override-commit=$NEWID --reboot
  7. Wait until the system is booted again and check the deployment
    8. $ sudo ostree admin status
  8. The booted commit (started with '*') must have ID which we prepare and the initial commit ID should be marked as '(rollback)'
  9. Remove the initial deployment
    10. $ sudo ostree admin undeploy 1
  10. Reboot the system
  11. Check the current deployment
    12. $ sudo ostree admin status
  12. Start the user interface agent with mode preventing automatic system reboot after update
    13. $ sudo updatectl --register-upgrade-handler &
  13. Enable network updates with CLI tool
    14. $ sudo updatectl --check-network-updates
  14. Check that the user interface agent reports the pending update

    15. ** Message: 21:31:26.117: Network connected: Yes

    ** Message: 21:31:26.123: Upgrade status: Checking

    ** Message: 21:31:28.057: Upgrade status: Downloading

    ** Message: 21:31:51.170: Upgrade status: Deploying

    ** Message: 21:32:11.879: An upgrade is pending

  15. After the update, the device does *not* reboot automatically
  16. Check if there is pending deployment and reboot the DUT
    17. $ sudo ostree admin status
    $ sudo reboot
  17. Check the current deployment has been updated and that the rollback entry points to the prepared deployment
    18. $ sudo ostree admin status
  18. Start the user interface agent
    19. $ sudo updatectl &
  19. Enable network updates with CLI tool
    20. $ sudo updatectl --check-network-updates
  20. Check that the user interface agent reports the system is up to update

    21. ** Message: 21:47:11.501: Network connected: Yes

    ** Message: 21:47:11.508: Upgrade status: Checking

    ** Message: 21:47:13.079: Upgrade status: Downloading

    ** Message: 21:47:13.080: System is up to date

Expected

CLI utility `updatectl` is able to interact with Apertis update manager

The OTA update was properly applied