apertis-update-manager-ota-check-network-failure manual

medium

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

Description

Test the apertis-update-manager API for updates over the air when the network is diconnected and reconnected.

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

Pre Conditions

  1. This test requires a properly configured time source: when testing devices not carrying a battery-backed real time clock in a network which prevents connections to NTP servers (and only in that case) manually ensure that the time on the device is set appropriately and that it is propagated to the hardware clock so it is stay set on the next reboot if the power is not plugged off.
    2. $ sudo timedatectl --adjust-system-clock set-time "2019-08-21 18:49:03"
  2. If direct access to repository with updates for DUT is restricted and proxy server should be used, then need to add the address of this proxy for OSTree on DUT by command:
    3. $ sudo ostree config set 'remote "origin"'.proxy "http://10.168.128.45:3128"

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

  15. Once the above message is seen disconnect the network connection to the target

    16. ** Message: 21:31:26:129: Network connected: No

  16. Re-establish the network connection to the target

    17. ** 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

  17. After the update, the device does *not* reboot automatically
  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. Enable network updates with CLI tool
    22. $ sudo updatectl --check-network-updates
  22. Check that the user interface agent reports the system is up to update

    23. ** 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 even if there's a network failure in between the updates

The OTA update was successfully applied