action #128261
open
[security] test fails in first_boot in lvm_full_encrypt on ppc64le
Added by tjyrinki_suse about 1 year ago.
Updated 23 days ago.
Category:
Bugs in existing tests
Description
Observation¶
update 15-SP5 QU: https://openqa.suse.de/tests/13992096
15-SP4 QU:
openQA test in scenario sle-15-SP4-Online-QR-ppc64le-fips_install_lvm_full_encrypt@ppc64le-hmc-single-disk fails in
reboot_after_installation
Always latest result in this scenario: latest
This has seemingly never passed in QU, but could now be debugged since ppc64le backend is more reliable. It now fails so that it never reaches first_boot.
Notably this same test suite passed 7 days ago in 15-SP5 at https://openqa.suse.de/tests/10938327 . But the schedule in 15-SP4 is completely different (earlier fork?) than in 15-SP5 while the YAML_TEST_DATA points to the same file. The latter might need to be forked too to a version that remains compatible with 15-SP4, if the cause from the problem is from that.
Related issues
1 (1 open — 0 closed)
The thing is that the test data is the same and has not been changed for years. It think it would be best if we were to fork the relevant yast tests (proven working), extending them to work with both beta and non-beta distributions and executing them in FIPS mode. We would then, of course, delete all of our old test schedules.
- Related to action #130228: [security] Extend encrypted install tests in FIPS for full-disk encryption added
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_install_lvm_full_encrypt
https://openqa.suse.de/tests/11575296#step/bootloader_start/1
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 bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_install_lvm_full_encrypt
https://openqa.suse.de/tests/11606180#step/bootloader_start/1
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 bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 64 days if nothing changes in this ticket.
- Parent task set to #135320
- Status changed from New to Workable
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_install_lvm_full_encrypt
https://openqa.suse.de/tests/11606180#step/bootloader_start/1
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 bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 80 days if nothing changes in this ticket.
- Status changed from Workable to Blocked
This is not workable as we don't have ppc64le workers at the moment.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_install_lvm_full_encrypt
https://openqa.suse.de/tests/11606180#step/bootloader_start/1
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 bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 68 days if nothing changes in this ticket.
- Description updated (diff)
- Status changed from Blocked to Workable
Also available in: Atom
PDF