apertis-update-manager-api manual

low

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

Description

Test the apertis-update-manager automatic update. The automated version of this test: https://qa.apertis.org/aum-api.html

Resources

  • A static update bundle file of the same architecture, variant and version as the testing image
  • A Fat32 USB flash drive, preloaded with the update bundle at the root of the disk
  • Downloaded update file (with '.delta' extension) should be copied to flash drive using the name 'static-update.bundle'
  • 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

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. Plug the USB flash drive into the device
  14. The update starts automatically
  15. After the update, the device does *not* reboot automatically
  16. Check that the user interface agent reports the pending update

    17. ** Message: Upgrade status: Checking

     ** Message: An upgrade is pending

  17. Remove the USB flash drive
  18. Check if there is pending deployment and reboot the DUT
    19. $ sudo ostree admin status
    $ sudo reboot
  19. Check the current deployment has been updated and that the rollback entry points to the prepared deployment
    20. $ sudo ostree admin status
  20. Start the user interface agent
    21. $ sudo updatectl &
  21. Plug the USB flash drive with the same update file into the device
  22. Check that the user interface agent reports the system is up to update

    23. ** Message: Upgrade status: Checking

    ** Message: System is up to date

Expected

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

The update was properly applied