action #157138
open
[security] SLE Micro 6.0 s390x tests do not start (container_selinux, selinux)
Added by tjyrinki_suse about 2 months ago.
Updated 8 days ago.
Category:
Bugs in existing tests
Description
openQA test in scenario sle-micro-6.0-Base-qcow-s390x-container_selinux@s390x-kvm fails in
disk_boot
This has not been tried to be executed before. It is likely trying to boot with wrong modules and possibly wrong settings, comparison can be done to https://openqa.suse.de/tests/13756869 which boots the same image successfully.
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: container_selinux
https://openqa.suse.de/tests/13756851#step/disk_boot/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.
- Status changed from Workable to In Progress
- Assignee set to jlausuch
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19121
The problem raises because of the limitation of yaml schedule of handling conditions.
The ideal solution would be:
if s390:
- installation/bootloader_start
- boot/boot_to_desktop
else:
if ENCRYPTED_IMAGE = 0
- microos/disk_boot
elsif ENCRYPTED_IMAGE = 0
- jeos/firstrun
but this can't be done in yaml, so what I did in the PR is working but it needs EXCLUDE_MODULES=disk_boot in s390x jobs... (or maybe set ENCRYPTED_IMAGE=null or some other value !=0|1)
Also available in: Atom
PDF