From 53c52046d883522423b1b1e97181ce10b8f5a55e Mon Sep 17 00:00:00 2001 From: Valentin David Date: Thu, 30 Jan 2025 10:47:17 +0100 Subject: [PATCH] tests/nested/core/core20-fault-inject-on-refresh: disable FDE (#14945) * tests/nested/core/core20-fault-inject-on-refresh: disable FDE Refresh from store get some kernel that have an old initrd that do not support FDE installation from new snapd. --- .../core/core20-fault-inject-on-refresh/task.yaml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/tests/nested/core/core20-fault-inject-on-refresh/task.yaml b/tests/nested/core/core20-fault-inject-on-refresh/task.yaml index 5e48686ed16..5f0e211733d 100644 --- a/tests/nested/core/core20-fault-inject-on-refresh/task.yaml +++ b/tests/nested/core/core20-fault-inject-on-refresh/task.yaml @@ -44,7 +44,15 @@ environment: FAULT/kernel_reboot_refresh_gadget_assets: reboot TAG/gadget_reboot_refresh_gadget_assets: refresh-gadget-assets FAULT/gadget_reboot_refresh_gadget_assets: reboot - + + # refresh from store might get some kernel that have an old + # initrd. The problem is that a new snapd in seed may require a + # new initrd. For instance when adding a new format of key in FDE. + # TODO: change it to use fakestore, so we can control all the + # snaps we use. + NESTED_ENABLE_SECURE_BOOT: false + NESTED_ENABLE_TPM: false + prepare: | # automatically cleaned up in restore echo "Inject a $FAULT on $TAG"