AUM tests show as failed due to error when parsing logs

Affected images versions

v2024dev2

Unaffected images versions

• all versions up to XXX (replace XXX with the build id of the most recent Apertis images where this bug cannot be reproduced)
• not relevant (explain why)
• v2022 (explain why)

Background

Tests for AUM show as failed https://qa.apertis.org/report/v2024dev2/20230620.0016/ostree

While checking log it is clear the AUM has restarted as expected but the logs were not parsed properly

https://lava.collabora.dev/scheduler/job/10824395#results_373777847

Reproducibility

How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?

Put the ✅ in the most appropriate entry:

1. ✅ always
2. often, but not always
3. rarely

Impact of bug

Tests show as failed

Root cause

The string printed by systemd after the rebase on top of Bookworm is different from the expected.

Outcomes

tests/aum-offline-upgrade!51 (merged)

Management data

This section is for management only, it should be the last one in the description.

/cc @andrunko @em @sagar @sudarshan @wlozano

Phabricator link: https://phabricator.apertis.org/T9838