action #56498
closed[migration][security] test fails in bootloader_zkvm
0%
Description
Observation¶
openQA test in scenario sle-15-SP2-Installer-DVD-s390x-fips_tests_crypt_install@s390x-kvm-sle15 fails in
bootloader_zkvm
Test suite description¶
Maintainer: bchou@suse.com
Reproducible¶
Fails since (at least) Build 3.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
In FIPS mode, this test should add "fips=1" to the commandline of the booted installer kernel.
I am making a simple patch.
Updated by msmeissn over 4 years ago
Updated by okurz over 4 years ago
- Status changed from New to Feedback
- Assignee set to msmeissn
merged. retriggered latest as https://openqa.suse.de/tests/3328246
Updated by SLindoMansilla over 4 years ago
- Status changed from Feedback to Workable
In the os-autoinst log from the reported job, there was already fips parameter used: https://openqa.suse.de/tests/3303561/file/autoinst-log.txt
ifcfg=dhcp install=ftp://openqa.suse.de/SLE-15-SP2-Installer-DVD-s390x-Build22.2-Media1 sshd=1 VNC=1 VNCSize=1024x768 VNCPassword=nots3cr3t sshpassword=nots3cr3t SetHostname=0 fips=1 regurl=http://all-22.2.proxy.scc.suse.de
So, I the problem wasn't a missing FIPS parameter to linuxrc.
The verification run is failing the same. And it shows the parameter duplicated: https://openqa.suse.de/tests/3328246/file/autoinst-log.txt
ifcfg=dhcp install=ftp://openqa.suse.de/SLE-15-SP2-Installer-DVD-s390x-Build27.1-Media1 sshd=1 VNC=1 VNCSize=1024x768 VNCPassword=nots3cr3t sshpassword=nots3cr3t fips=1 SetHostname=0 fips=1 regurl=http://all-27.1.proxy.scc.suse.de
Updated by SLindoMansilla over 4 years ago
- Subject changed from test fails in bootloader_zkvm to [migration] test fails in bootloader_zkvm
Updated by okurz over 4 years ago
- Subject changed from [migration] test fails in bootloader_zkvm to [migration][security] test fails in bootloader_zkvm
- Assignee deleted (
msmeissn)
I see. revert in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8381 . Please merge that if you can approve. @msmeissn, removed you again as I assume it's a bit harder. IMHO the ticket is more fitting for "[security]" than "[migration]".
Updated by llzhao about 4 years ago
- Status changed from Workable to Resolved
AFAIK, it was resolved by "Matthias Griessmeier" now.
It is testing hypervisor issue.