action #97289
openQA Tests - coordination #96302: [qe-core][QU] Quarterly update failures
[qem][qu] test fails in await_install in 15-SP3 QU
0%
Description
Observation¶
openQA test in scenario sle-15-SP3-Online-QR-ppc64le-crypt_no_lvm@ppc64le fails in
await_install
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: https://openqa.suse.de/tests/6872059 https://openqa.suse.de/tests/6872114
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.
Reproducible¶
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
History
#1
Updated by tjyrinki_suse almost 2 years ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
#2
Updated by tjyrinki_suse almost 2 years ago
- Parent task set to #96302
#3
Updated by openqa_review almost 2 years 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
https://openqa.suse.de/tests/6903766
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
#4
Updated by oorlov over 1 year 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 over 1 year ago
we have seen it in latest product validation, it is a Out of memory issue, referenced bug: https://bugzilla.suse.com/show_bug.cgi?id=1189707
#6
Updated by JERiveraMoya over 1 year ago
- Tags deleted (
qe-yast-refinement) - Assignee set to oorlov
#7
Updated by oorlov over 1 year ago
- Status changed from New to Blocked
- Priority changed from High to Normal
#8
Updated by oorlov over 1 year ago
- Assignee changed from oorlov to JERiveraMoya
#9
Updated by JERiveraMoya 11 months ago
- Tags set to YaST
- Status changed from Blocked to New
- Assignee deleted (
JERiveraMoya) - Priority changed from Normal to Low
Moved to backlog, to be check in the near future.
#10
Updated by JERiveraMoya 8 months ago
- Target version changed from Current to future
#11
Updated by JERiveraMoya 8 months ago
- Target version deleted (
future)
#12
Updated by szarate 6 months ago
- Status changed from New to Rejected
- Assignee set to szarate
All good according to: https://bugzilla.suse.com/show_bug.cgi?id=1189707#c30