From 2ebc6226a471eb669e55b83940a1998cb801f635 Mon Sep 17 00:00:00 2001 From: Krisztian Litkey Date: Fri, 26 Jun 2026 09:20:18 +0300 Subject: [PATCH] e2e: use nop BTRFS/blob corruption handlers for cri-o. It looks like the post-reboot BTRFS/blob corruption bug is not triggered with cri-o as a runtime, only with containerd as surprising as this may sound considering that it is an fs-level corruption (unreadable blob file). Anyway, switch the cri-o-specfic handlers to mere logging nops for now. We'll revert this and look into it again if we ever see it triggered. Signed-off-by: Krisztian Litkey --- test/e2e/lib/vm.bash | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/test/e2e/lib/vm.bash b/test/e2e/lib/vm.bash index 856d804db..c1da54bb6 100644 --- a/test/e2e/lib/vm.bash +++ b/test/e2e/lib/vm.bash @@ -1119,13 +1119,13 @@ containerd-reimport-image() { } crio-check-unreadable-blobs() { - error "TODO: implement unreadable blob check for CRI-O..." + echo "TODO: implement unreadable blob check for CRI-O... assuming no errors for now" } crio-fix-unreadable-blobs() { - error "TODO: implement unreadable blob fix for CRI-O (if possible)..." + echo "TODO: implement unreadable blob fix for CRI-O (if possible)... assuming no-op for now" } crio-reimport-image() { - error "TODO: implement image reimport for CRI-O..." + echo "TODO: implement image reimport for CRI-O... assuming no-op for now" }