AUM tests fail in v2024dev1 due to signature problems

Affected images versions

• not relevant (explain why)
• see the table below (list the build id and the apt or ostree deployment of the tested images in the appropriate cells)

Type	Arch	v2022	v2023	v2024dev1
minimal/fixedfunction	amd64			ostree
minimal/fixedfunction	armhf			ostree
minimal/fixedfunction	arm64			ostree
target/hmi	amd64
target/hmi	armhf
target/hmi	arm64
basesdk	amd64
sdk	amd64
nfs	amd64
nfs	armhf
nfs	arm64
lxc	amd64
lxc	armhf
lxc	arm64
image-builder
package-source-builder

To find the build id and the variant type you can:

• derive it from the image name
  • for instance, with the apertis_ostree_v2022pre-fixedfunction-amd64-uefi_20211031.0425.img.gz image the build id is 20211031.0425, the variant is fixedfunction the deployment type is ostree
• obtain it from /etc/os-release using the BUILD_ID and VARIANT_ID keys

Unaffected images versions

Versions earlier than v2024dev1

Testcase

https://qa.apertis.org/testcases/v2024dev1/aum-api.html https://qa.apertis.org/testcases/v2024dev1/aum-offline-upgrade.html https://qa.apertis.org/testcases/v2024dev1/aum-offline-upgrade-branch.html

Steps to reproduce

Ordered list detailing every step so other developers can reproduce the issue. Include hardware which you used.

• ...

Expected result

Test should pass

Actual result

Upgrade fails due to signature issues

Jan 05 03:00:21 apertis apertis-update-[573]: Commit in static delta have no valid signature; aborted
+ journalctl --after-cursor s=44b459c509794861bc06e7ad052a986c;i=2fe;b=4931c3a21c994fef83e5446208fd66b1;m=3b0e103;t=5f17b7e92547e;x=5e318d17709842c9+  --unitgrep -qE Ostree already up to date
 apertis-update-manager
+ journalctl --after-cursor s=44b459c509794861bc06e7ad052a986c;i=2fe;b=4931c3a21c994fef83e5446208fd66b1;m=3b0e103;t=5f17b7e92547e;x=5e318d17709842c9 --unit apertis-update-manager
+ grep -qE Ostree upgrade failed
+ journalctl --after-cursor s=44b459c509794861bc06e7ad052a986c;i=2fe;b=4931c3a21c994fef83e5446208fd66b1;m=3b0e103;t=5f17b7e92547e;x=5e318d17709842c9+  --unit apertis-update-managergrep -qE Starting Apertis update manager
+ journalctl --after-cursor s=44b459c509794861bc06e7ad052a986c;i=2fe;b=4931c3a21c994fef83e5446208fd66b1;m=3b0e103;t=5f17b7e92547e;x=5e318d17709842c9 --unit apertis-update-manager
+ grep -qE Ostree upgrade ready, system should be rebooted
+ sleep 5
AUM-Message: 03:00:27.161: Upgrade status: Unknown
Jan 05 03:00:27 apertis apertis-update-managerd[573]: Freed objects: 388 bytes
Jan 05 03:00:27 apertis apertis-update-[573]: Ostree upgrade failed: ed25519: commit have no signatures of my type
+ journalctl --after-cursor s=44b459c509794861bc06e7ad052a986c;i=2fe;b=4931c3a21c994fef83e5446208fd66b1;m=3b0e103;t=5f17b7e92547e;x=5e318d17709842c9 --unit apertis-update-manager
+ grep -qE Ostree already up to date
+ journalctl --after-cursor s=44b459c509794861bc06e7ad052a986c;i=2fe;b=4931c3a21c994fef83e5446208fd66b1;m=3b0e103;t=5f17b7e92547e;x=5e318d17709842c9 --unit apertis-update-manager
+ grep -qE Ostree upgrade failed
+ echo update failed
update failed

https://lava.collabora.dev/scheduler/job/8582314#L8364

Examples: https://lava.collabora.dev/results/8582314/9_aum-api https://lava.collabora.dev/results/8582315/9_aum-offline-upgrade https://lava.collabora.dev/results/8582316/9_aum-offline-upgrade-branch

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

How severe is the bug? Does it render an image unbootable? Is it a security issue? Does it prevent specific applications from working? What is the impact? Does this bug affect a critical component? Does it cause something else to not work? How often is the bug likely to be found by a user? For example, every boot or once per year?

Attachments

Add further information about the environment in the form of attachments here. Attach plain text files from log output (from journalctl, systemctl, …) or long backtraces as attached files. If adding comments on the log is required create a new snippet and add the link to it here.

Screenshots and videos are usually useful for graphic issues.

Root cause

describe in one line what caused the issue to give a hint to product teams whether they may be impacted or not

Outcomes

TBD

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/T9509