apertis-update-manager-diskfull manual

low

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

Description

Ensure that failures due to disk full errors during updates have no effect on the system The automated version of this test: https://qa.apertis.org/aum-out-of-space.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
  • 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
  • The static update file should be copied to the flash drive using the name 'static-update.bundle'.
  • 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 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. Need to monitor the journal log
    15. $ sudo journalctl -ef --unit apertis-update-manager &
  15. Check the free space on rootfs, calculate the size of file to leave insufficient free space for upgrade to happen (this prevents the unexpected reboot during the test caused by other services). For instance, in the case below, NUM value would be 1451. It is the result of the calculation 1823-348-24, there 24 is a magic constant, so that almost, but not all free space is used. The free space can be calculated with command line `sudo df -B 1M / | grep / | awk '{print $2-$3-24}'`
    16. $ sudo df -B 1M /

    Filesystem           1M-blocks      Used Available Use% Mounted on

    /dev/mmcblk0p2            1823       348      1365  21% /

    $ sudo dd if=/dev/zero of=/var/bigfile bs=1M count=<NUM> ; echo "dd completed!"
  16. Wait until 'dd' completes (it should take time), you will see the output similar to

    17. 1521483776 bytes (1.5 GB) copied, 82.1661 s, 18.5 MB/s

    dd completed!

  17. Plug the USB flash drive in the device
  18. The update should fail with error message

    19. Dec 19 22:53:33 apertis apertis-update-[348]: Ostree upgrade failed: min-free-space-percent '3%' would be exceeded, 16.8 MB available

  19. Remove the USB flash drive
  20. Set reserved space for ostree to '0'
    21. $ sudo ostree config set core.min-free-space-percent "0"
  21. Restart the Apertis Update Manager
    22. $ sudo systemctl restart apertis-update-manager
  22. Plug the USB flash drive in the device
  23. The update should fail with some error message related to disk space, for instance:

    24. Dec 19 22:55:10 apertis apertis-update-[319]: Ostree upgrade failed: mkdir(boot/loader.0/entries): Input/output error

    Dec 19 22:43:46 apertis apertis-update-[794]: Ostree upgrade failed: Error writing to file descriptor: No space left on device

  24. Remove the USB flash drive
  25. Remove temporary file
    26. $ sudo rm -f /var/bigfile
  26. Reboot the system
    27. $ sudo reboot
  27. Check that the status is the same than at the beginning of the test
    28. $ sudo ostree admin status

Expected

The update wasn't applied

System boots using the initial deployment