AUM OTA: add the command for progress checking

Use a single step for reboot waiting. Added the example how to track the
upgrade status while waiting for automatic upgrade and reboot.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

test-cases/apertis-update-manager-ota-auto.yaml

@@ -50,8 +50,22 @@ run:
     - $ sudo rm -f /var/aum_blacklist.conf
     - "Reboot the system"
     - $ sudo reboot
-    - "Wait while the system booted successfully."
-    - "Need to wait a short time (30-120 sec) depending on your network. The update must be downloaded and the system should be rebooted second time automatically."
+    - "Wait while the system booted successfully. Need to wait a short time (30-120 sec) depending on your network. The update must be downloaded and the system should be rebooted second time automatically.
+      The current status of upgrade could be checked with journalctl log -- it should not contain error messages about the upgrade. The listing below is just for example:"
+    - $ sudo journalctl -ef --unit apertis-update-manager
+    - |
+        >Jun 01 11:54:26 apertis apertis-update-[355]: Ostree upgrade progress: 1 metadata, 0 content objects fetched
+        Jun 01 11:54:26 apertis apertis-update-[355]: Cannot check the ID in black list: No such file or directory
+        Jun 01 11:57:10 apertis apertis-update-managerd[355]: libostree pull from 'origin' for apertis/v2019pre/amd64-uefi/minimal complete
+                                                              security: GPG: disabled http: TLS
+                                                              non-delta: meta: 23 content: 39
+                                                              transfer: secs: 163 size: 32.2 MB
+        Jun 01 11:57:10 apertis apertis-update-[355]: New upgrade downloaded! Deploying..
+        Jun 01 11:57:10 apertis apertis-update-managerd[355]: Copying /etc changes: 13 modified, 0 removed, 1 added
+        Jun 01 11:57:10 apertis apertis-update-[355]: Couldn't unlink ostree-0-1.conf
+        Jun 01 11:57:11 apertis apertis-update-managerd[355]: Transaction complete; bootconfig swap: yes; deployment count change: 1
+        Jun 01 11:57:11 apertis apertis-update-[355]: Ostree upgrade ready, system should be rebooted
+        Jun 01 11:57:11 apertis apertis-update-[355]: Rebooting to apply pending update
     - "Check the current deployment has been updated and that the rollback entry points to the prepared deployment"
     - $ sudo ostree admin status
     - "Check the journal log should mention that the system check the update availability and report it is already up to date"