action #97289

openQA Tests - coordination #96302: [qe-core][QU] Quarterly update failures

[qem][qu] test fails in await_install in 15-SP3 QU

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

Target version:
Start date:
Due date:
% Done:


Estimated time:



openQA test in scenario sle-15-SP3-Online-QR-ppc64le-crypt_no_lvm@ppc64le fails in

This was passing in 188.13 which was before git commit "Fix YaST-related tests in QR Updates for SP3", maybe even if not directly affected something was changed around that time that fixed others but broke this?

It is however passing for aarch64 and x86:

Test suite description

Maintainer: riafarov. Test installation with encrypted partitions but without lvm enabled. This is supported only by storage-ng, hence, do NOT enable test suite on distris without storage-ng.

(crypt-)LVM installations can take longer, especially on non-x86_64 architectures.


Fails since (at least) Build 188.14

Expected result

Last good: 188.13 (or more recent)

Further details

Always latest result in this scenario: latest


#1 Updated by tjyrinki_suse 9 months ago

  • Project changed from openQA Tests to qe-yast
  • Category deleted (Bugs in existing tests)

#2 Updated by tjyrinki_suse 9 months ago

  • Parent task set to #96302

#3 Updated by openqa_review 9 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: crypt_no_lvm

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#4 Updated by oorlov 8 months ago

  • Tags set to qe-yast-refinement
  • Subject changed from [qe-yast][qem][qu] test fails in await_install in 15-SP3 QU to [qem][qu] test fails in await_install in 15-SP3 QU
  • Priority changed from Normal to High
  • Target version set to Current

We need to identify it if is a product bug or an infrastructure issue.

#5 Updated by JERiveraMoya 8 months ago

we have seen it in latest product validation, it is a Out of memory issue, referenced bug:

#6 Updated by JERiveraMoya 8 months ago

  • Tags deleted (qe-yast-refinement)
  • Assignee set to oorlov

#7 Updated by oorlov 7 months ago

  • Status changed from New to Blocked
  • Priority changed from High to Normal

#8 Updated by oorlov 3 months ago

  • Assignee changed from oorlov to JERiveraMoya

Also available in: Atom PDF