AUM: add dry-run mode and check counter for OTA manual test

Added the `dry-run` mode feature testing.
Added the network polling time change feature testing.
Updated output for manual OTA rollback upgrade test.

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

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

@@ -65,15 +65,24 @@ run:
     - $ sudo rm -f /var/aum_blacklist.conf
     - "Start the user interface agent with mode preventing automatic system reboot after update"
     - $ sudo updatectl --register-upgrade-handler &
+    - "Check if network update is available"
+    - $ sudo updatectl --check-network-updates --dry-run
+    - |
+        >AUM-Message: 09:38:03.883: Network connected: Yes
+         AUM-Message: 09:38:03.890: Upgrade status: Checking
+         AUM-Message: 09:38:03.890: Upgrade status: Checking
+         AUM-Message: 09:38:05.967: Upgrade status: Available
     - "Enable network updates with CLI tool"
     - $ sudo updatectl --check-network-updates
     - "Check that the user interface agent reports the pending update"
     - |
-        >** Message: 21:31:26.117: Network connected: Yes
-        ** Message: 21:31:26.123: Upgrade status: Checking
-        ** 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
+        >AUM-Message: 09:41:03.263: Network connected: Yes
+        AUM-Message: 09:41:03.268: Upgrade status: Checking
+        AUM-Message: 09:41:03.269: Upgrade status: Checking
+        AUM-Message: 09:41:04.503: Upgrade status: Available
+        AUM-Message: 09:41:04.505: Upgrade status: Downloading
+        AUM-Message: 09:41:16.943: Upgrade status: Deploying
+        AUM-Message: 09:41:35.660: An upgrade is pending
     - "After the update, the device does *not* reboot automatically"
     - "Check if there is pending deployment and reboot the DUT"
     - $ sudo ostree admin status
@@ -102,22 +111,32 @@ run:
     - $ cat /var/aum_blacklist.conf
     - |
         >[blacklist]
-        1239e167bddff9464efd58695ea15edff6679964aee20e1b1b9d6a126bd66941=true
+        7dfbc519eea384ed357920f733b051e1b06175834cbfdc1d6ef034bf7a5500ee=true
     - "Start the user interface agent"
     - $ sudo updatectl &
-    - "Enable network updates with CLI tool"
-    - $ sudo updatectl --check-network-updates
+    - "Enable network updates with CLI tool with setting the update delay"
+    - $ sudo updatectl --check-network-updates 15
     - "Check that the user interface agent reports the system is up to update"
     - |
-        >** 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
+        >AUM-Message: 09:47:19.339: Network connected: Yes
+        AUM-Message: 09:47:19.343: Upgrade status: Checking
+        AUM-Message: 09:47:19.344: Upgrade status: Checking
+        AUM-Message: 09:47:21.100: Upgrade status: Available
+        AUM-Message: 09:47:21.101: System is up to date
     - "Check the journal log should mention that the update ID has been blacklisted"
-    - $ sudo journalctl -ef --unit apertis-update-manager
+    - $ sudo journalctl -ef --unit apertis-update-manager --no-pager
     - |
-        >Jun 01 22:01:46 apertis apertis-update-[365]: Auto update status: active
-        Jun 01 22:01:46 apertis apertis-update-[365]: Ostree upgrade poll starting
-        Jun 01 22:01:47 apertis apertis-update-[365]: Ostree upgrade progress: 1 metadata, 0 content objects fetched
-        Jun 01 22:01:47 apertis apertis-update-[365]: Revision '1239e167bddff9464efd58695ea15edff6679964aee20e1b1b9d6a126bd66941' is marked as blacklisted; skipping
-        Jun 01 22:01:47 apertis apertis-update-[365]: Ostree already up to date
+        > Apr 29 09:47:19 apertis apertis-update-[485]: Auto update status: active
+        Apr 29 09:47:19 apertis apertis-update-[485]: Ostree upgrade poll starting
+        Apr 29 09:47:21 apertis apertis-update-managerd[485]: libostree pull from 'origin' for apertis/v2022dev1/armhf-uboot/minimal complete
+                                                              security: GPG: disabled 
+                                                              security: SIGN: commit http: TLS
+                                                              non-delta: meta: 1 content: 0
+                                                              transfer: secs: 1 size: 95 bytes
+        Apr 29 09:47:21 apertis apertis-update-managerd[485]: 1 metadata, 0 content objects fetched; 95 B transferred in 1 seconds; 0 bytes content written
+        Apr 29 09:47:21 apertis apertis-update-[485]: Network upgrade is available
+        Apr 29 09:47:21 apertis apertis-update-[485]: Revision '7dfbc519eea384ed357920f733b051e1b06175834cbfdc1d6ef034bf7a5500ee' is marked as blacklisted; skipping
+        Apr 29 09:47:21 apertis apertis-update-[485]: Ostree already up to date
+    - Wait for 20 seconds, you should to see the update is triggered again and
+      the output is similar to steps above.
+