action #87704
closed[qe-core][qem][QU] test fails in boot_encrypt on s390x (and only s390x)
0%
Description
Observation¶
openQA test in scenario sle-15-SP2-Online-QR-s390x-lvm-encrypt-separate-boot@s390x-kvm-sle12 fails in
boot_encrypt
Test suite description¶
Same as lvm-full-encrypt, but with separate boot not encrypted partition, only installation to not repeat everything again with small risk.
Maintainer: riafarov
Reproducible¶
Fails since (at least) Build 377.1
Expected result¶
Last good: 376.16 (or more recent)
--
Note: also this passing is already using the separated QAM YAML schedule schedule/qam/QR/lvm_encrypt_separate_boot.yaml
--
Further details¶
Always latest result in this scenario: latest
Updated by tjyrinki_suse about 4 years ago
- Subject changed from [qe-core][qem][qr] test fails in boot_encrypt to [qe-core][qem][QU] test fails in boot_encrypt
Updated by tjyrinki_suse about 4 years ago
- Subject changed from [qe-core][qem][QU] test fails in boot_encrypt to [qe-core][qem][QU] test fails in boot_encrypt on s390x (and only s390x)
This started happening around after lvm update https://smelt.suse.de/incident/16878/ landed.
Updated by tjyrinki_suse about 4 years ago
Filed https://bugzilla.suse.com/show_bug.cgi?id=1180973 to investigate from product side.
Edit: Booting with plymouth.enable=0 does pass (done manually by Sergio at https://openqa.suse.de/tests/5326537#step/boot_encrypt/5), so it's a change of behavior but the encrypt functionality itself is intact. Discussion continues on the bug side.
Updated by tjyrinki_suse about 4 years ago
- Status changed from Workable to Resolved
This should be fixed by bug fix, no test changes should be needed.