action #128252
closed[security] test fails in logs_from_installation_system in lvm_encrypt_separate_boot in 15-SP4 QU3 on s390x
0%
Description
Observation¶
openQA test in scenario sle-15-SP4-Online-QR-s390x-fips_install_lvm_encrypt_separate_boot@s390x-kvm-sle12 fails in
logs_from_installation_system
This is an old issue but I don't see an existing ticket for it.
Updated by tjyrinki_suse over 1 year ago
- Subject changed from [security] test fails in logs_from_installation_system in 15-SP4 QU3 on s390x to [security] test fails in logs_from_installation_system in lvm_encrypt_separate_boot in 15-SP4 QU3 on s390x
Updated by amanzini over 1 year ago
- Status changed from New to Blocked
Since we are also working on refactoring the schedules, better to wait for a stable situation before proceeding.
Updated by openqa_review over 1 year ago
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_encrypt_separate_boot
https://openqa.suse.de/tests/11051880#step/logs_from_installation_system/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.
Updated by amanzini over 1 year ago
- Assignee deleted (
amanzini)
unassigning due to squad rotation - Andrea visiting SAP/HANA Perf squad
Updated by tjyrinki_suse over 1 year ago
- Status changed from Blocked to Workable
@emiler You may want to check if this ticket is a duplicate of some other ticket.
Updated by JERiveraMoya over 1 year ago
no test suite or iso to work on this one. Please add more info if still a valid ticket.
Updated by JERiveraMoya about 1 year ago
missing test module to stop reboot timeout: https://openqa.suse.de/tests/12119069#step/stop_timeout_system_reboot_now/1
that is the reason why the logs cannot be retrieved because the system is rebooting/reconnecting at that time, not console available.
Updated by JERiveraMoya about 1 year ago
- Status changed from Workable to Rejected
Even a bit more messy, the test suite was renamed, so it is actually a different error happening in QU3 but also in product:
https://openqa.suse.de/tests/11605903#step/accept_license/2
https://openqa.suse.de/tests/12203709#step/accept_license/2
Fixed by Emil here https://progress.opensuse.org/issues/137018 as QU3 is using the same schedule than product.
Rejecting ticket.