Project

General

Profile

action #87704

[qe-core][qem][QU] test fails in boot_encrypt on s390x (and only s390x)

Added by tjyrinki_suse 10 months ago. Updated 9 months ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

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

History

#1 Updated by tjyrinki_suse 10 months ago

  • Subject changed from [qe-core][qem][qr] test fails in boot_encrypt to [qe-core][qem][QU] test fails in boot_encrypt

#2 Updated by tjyrinki_suse 10 months ago

  • Status changed from New to Workable

#3 Updated by tjyrinki_suse 10 months ago

  • Priority changed from Normal to High

#4 Updated by tjyrinki_suse 10 months ago

  • Description updated (diff)

#5 Updated by tjyrinki_suse 9 months 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.

#6 Updated by tjyrinki_suse 9 months 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.

#7 Updated by tjyrinki_suse 9 months ago

  • Status changed from Workable to Resolved

This should be fixed by bug fix, no test changes should be needed.

Also available in: Atom PDF