action #160841
closedcoordination #151816: [epic] Handle openQA fixes and job group setup
test fails in validate_encrypt
0%
Description
Observation¶
Continuation of https://progress.opensuse.org/issues/160153
the remaining install options now also switched to luks2 (control files updated)
This error showed up in 3 tests or so
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-cryptlvm@64bit fails in
validate_encrypt
Test suite description¶
Maintainers: QE Yast
Conduct installation with encrypted LVM selected during installation.
Reproducible¶
Fails since (at least) Build 20240523 (current job)
Expected result¶
Last good: 20240522 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dimstar 5 months ago
two out of the three are 'easy':
https://github.com/os-autoinst/opensuse-jobgroups/pull/462
the third one (crypt_no_lvm) fails with this data set, as tested at
https://openqa.opensuse.org/tests/4218635#step/validate_encrypt/15
Updated by JERiveraMoya 5 months ago ยท Edited
- Tags set to qe-yam-may-sprint
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests) - Status changed from New to Workable
- Parent task set to #151816
after https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19306
ramaining part should be only the crypt no lvm which didn't have updated test data. QE Yam squad will address it.
Updated by JERiveraMoya 5 months ago
- Status changed from Workable to In Progress
- Assignee set to leli
@leli I was expecting that (only I noticed after merging!), we should have run verification for the others, still needs further adjustments:
https://openqa.opensuse.org/tests/4219423#step/validate_encrypt/9
Updated by leli 4 months ago
Create a new test_data for 'crypt_no_lvm', and recover the encrypted device num for test_data/yast/encryption/full_lvm_enc_luks2,yaml. PR submitted https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19387
Updated by dimstar 4 months ago
leli wrote in #note-5:
Create a new test_data for 'crypt_no_lvm', and recover the encrypted device num for test_data/yast/encryption/full_lvm_enc_luks2,yaml. PR submitted https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19387
As that PR has been merged, I'm not sure if the expectation is that things are all right now. So just feedback from snapshot 0527:
- crytplvm: https://openqa.opensuse.org/tests/4226742#step/validate_encrypt/1 (failed)
Updated by leli 4 months ago
cryptlvm on TW should be luks2, crypt_no_lvm on leap should be luks1. We don't change files used, just update the test suites in product. PR submitted, https://github.com/os-autoinst/opensuse-jobgroups/pull/466
Updated by JERiveraMoya 4 months ago
could you please check if all the jobs in prod passed and resolve this ticket if so? thx.
Updated by ggardet_arm 4 months ago
It passed on aarch64: https://openqa.opensuse.org/tests/4229530
Updated by leli 4 months ago
- Status changed from In Progress to Resolved
All passed now:
TW:
https://openqa.opensuse.org/tests/4230328# cryptlvm
https://openqa.opensuse.org/tests/4230327# cryptlvm@uefi
https://openqa.opensuse.org/tests/4226801 crypt_no_lvm
leap:
https://openqa.opensuse.org/tests/4230333# crypt_no_lvm
https://openqa.opensuse.org/tests/4220924 cryptlvm
https://openqa.opensuse.org/tests/4220902 cryptlvm
So we can resolve this ticket now.