action #116281
closed[security][fips] test fails in boot_encrypt
0%
Description
Observation¶
# wait_serial expected: "Please enter passphrase for disk.*"
# Result:
version 2.06
[?25h Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device or file completions.
grub>
grub>
# Test died: Could not find "enter passphrase" prompt at sle/lib/utils.pm
Same test passes in yast. This is scheduled for the first time under fips, so it needs to be checked.
openQA test in scenario sle-15-SP5-Online-s390x-fips_install_lvm_encrypt_separate_boot@s390x-kvm-sle12 fails in
boot_encrypt
Test suite description¶
maintainer: richard.fan@suse.com
copy the case from yast team to test with FIPS mode
Reproducible¶
Fails since (at least) Build 15.2
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by openqa_review over 2 years 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/9516721#step/boot_encrypt/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 openqa_review about 2 years 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/9563449#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.
Updated by amanzini about 2 years ago
- Status changed from New to In Progress
- Assignee set to amanzini
Updated by amanzini about 2 years ago
- Status changed from In Progress to Blocked
Updated by openqa_review about 2 years 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/9823623#step/boot_encrypt/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 about 2 years ago
- Related to action #120249: [security][15sp4][QU1] test fails in boot_encrypt on s390x added
Updated by openqa_review about 2 years 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/9961180#step/boot_encrypt/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 openqa_review about 2 years 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/10028156#step/boot_encrypt/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 openqa_review about 2 years 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/10185371#step/boot_encrypt/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 56 days if nothing changes in this ticket.
Updated by openqa_review almost 2 years 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/10523529#step/boot_encrypt/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 112 days if nothing changes in this ticket.
Updated by tjyrinki_suse over 1 year ago
Bug is claimed to be fixed now.
A month ago in Build93.2 this still happened:
https://openqa.suse.de/tests/10952994#step/boot_encrypt/9
22 days ago in Build96.1 it looked similar on casual look, but is actually now different:
https://openqa.suse.de/tests/11020407#step/boot_encrypt/7
"dracut: FATAL: You have to specify boot= as a boot option for fips=1"
Updated by tjyrinki_suse over 1 year ago
- Status changed from Blocked to Workable
Updated by emiler over 1 year ago
It looks like we could use https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/installation/edit_optional_kernel_cmd_parameters.pm to inject boot= to kernel parameters using OPT_KERNEL_PARAMS. Running tests now.
Updated by emiler over 1 year ago
Alright, issue has been fixed by the suggested change: https://openqa.suse.de/tests/11211502#
Although it will be introduced in production with my new encryption tests, which are being tracked in https://progress.opensuse.org/issues/113162, branch https://github.com/realcharmer/os-autoinst-distri-opensuse/tree/encrypt
Updated by emiler over 1 year ago
- Related to action #113162: [security][FIPS][15-SP4][15-SP5] Implement & Integrate LUKS test case into openQA added
Updated by emiler over 1 year ago
Fix introduced in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17182 and waiting for being finished, merged and scheduled.
Updated by emiler over 1 year ago
- Status changed from In Progress to Resolved
New schedule merged. The original test will soon be removed, but this case is now covered in the new test, for example https://openqa.suse.de/tests/11227147.
Updated by tjyrinki_suse over 1 year ago
- Tags changed from fail to fail, encrypt
- Parent task set to #135320