From d4e11f30bcfb9c781c7c4e4415b5542347cdeada Mon Sep 17 00:00:00 2001 From: Frantisek Sumsal Date: Tue, 9 Apr 2024 14:04:28 +0200 Subject: [PATCH] test: forward journal to console in TEST-24-CRYPTSETUP If we fail to mount the encrypted /var during boot we're left with nothing to debug, so let's do the same thing we do for TEST-08-INITRD and forward journal to the console. --- test/TEST-24-CRYPTSETUP/test.sh | 3 +++ 1 file changed, 3 insertions(+) diff --git a/test/TEST-24-CRYPTSETUP/test.sh b/test/TEST-24-CRYPTSETUP/test.sh index 757c39a449d..93b447f583d 100755 --- a/test/TEST-24-CRYPTSETUP/test.sh +++ b/test/TEST-24-CRYPTSETUP/test.sh @@ -18,6 +18,9 @@ KERNEL_OPTIONS=( "luks.name=$PART_UUID=$DM_NAME" "luks.key=$PART_UUID=/keyfile:LABEL=varcrypt_keydev" "luks.options=$PART_UUID=x-initrd.attach" + # Forward journal to console to make debugging easier (or possible at all) if we fail to bring the + # encrypted /var up during boot + "systemd.journald.forward_to_console=1" ) KERNEL_APPEND+=" ${KERNEL_OPTIONS[*]}" QEMU_OPTIONS+=" -drive format=raw,cache=unsafe,file=${STATEDIR:?}/keydev.img"