apertis-update-manager manual

low

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

Description

Test the manual update with apertis-update-manager. The automated version of this test: https://qa.apertis.org/aum-offline-upgrade.html

Resources

  • A PC must be connected to DUT serial port
  • A static update bundle file of the same architecture, variant and version as the testing image
  • The latest static update file can be downloaded at the same location than the target image. It has the same basename, and a '.delta' extension

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 list of files to skip and enshure there are some files in these directories
    6. $ ls -1d /usr/share/locale /usr/share/man /usr/share/zoneinfo > /tmp/skip
    $ du -sh /usr/share/locale /usr/share/man /usr/share/zoneinfo
  6. Create the commit with changed timestamp and skipped list from above to allow upgrade with recent update file
    7. $ export NEWID=$(sudo ostree commit --orphan --tree=ref=$BOOTID --add-metadata-string=ostree.collection-binding=$CID --bind-ref=$REF --timestamp="1 year ago" --skip-list=/tmp/skip); echo "New commit: $NEWID"
  7. Deploy the prepared commit
    8. $ sudo ostree admin upgrade --allow-downgrade --deploy-only --override-commit=$NEWID --reboot
  8. Wait until the system is booted again and check the deployment
    9. $ sudo ostree admin status
  9. The booted commit (started with '*') must have ID which we prepare and the initial commit ID should be marked as '(rollback)'
  10. Check booted deployment have no file objects which we skip
    11. $ du -sh /usr/share/locale /usr/share/man /usr/share/zoneinfo
  11. Remove the initial deployment
    12. $ sudo ostree admin undeploy 1
  12. Reboot the system
  13. Check the current deployment
    14. $ sudo ostree admin status
  14. Remove blacklist file if it exists
    15. $ sudo rm -f /var/aum_blacklist.conf
  15. From the host, copy the static delta update to the target using scp
    16. $ scp /path/to/static/delta user@target:update.bundle
  16. The update does not start automatically, start it manually
    17. $ sudo updatectl --apply-static-delta /home/user/update.bundle
  17. After the update, the device will reboot automatically
  18. Check the current deployment has been updated and that the rollback entry points to the prepared deployment
    19. $ sudo ostree admin status

Expected

The update was properly applied