action #151393
closed[qe-core] test fails in boot_encrypt - grub will not ask twice for password anymore
0%
Description
Observation¶
Boot is now expected to continue without being asked for the LUKS passphrase in the initramfs as it's passed through via GRUB. See this comment for more details: https://build.suse.de/request/show/313273#comment-3963770
openQA test in scenario sle-15-SP6-Online-V-Staging-x86_64-cryptlvm_minimal_x@64bit fails in
boot_encrypt
Test suite description¶
Maintainer: slindomansilla
Combination of "cryptlvm" and "minimal_x".
(crypt-)LVM installations can take longer, especially on non-x86_64 architectures.
Reproducible¶
Fails since (at least) Build V.72.2
Expected result¶
Last good: V.72.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
This is due to grub2 update, see SR#313295: https://build.suse.de/request/show/313295
Boot is now expected to continue without being asked for the LUKS passphrase in the initramfs as it's passed through via GRUB. See this comment for more details: https://build.suse.de/request/show/313273#comment-3963770
Updated by pcervinka 5 months ago
This new feature needs more code changes, not just change in boot_encrypt. See failure in standard boot_to_desktop https://openqa.suse.de/tests/12948511#step/boot_to_desktop/11
Updated by szarate 5 months ago
- Subject changed from test fails in boot_encrypt to test fails in boot_encrypt -
So looks like we need to bring back https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18206 and adapt for boot to desktop
Updated by amanzini 5 months ago
- Related to action #117811: [opensuse] test fails in boot_encrypt: Skip boot_encrypt with new grub2 submission added
Updated by rfan1 5 months ago ยท Edited
As per discussion at https://suse.slack.com/archives/C02CSAZLAR4/p1701762005609789
The grub2 package with new patch has been checked to sle15sp6 product except some staging one due to ibs sync issue.
So I will try to continue this ticket to see if we can enhance the logic to check if we need to type_passwd again. especially for function is_boot_encrypted
Updated by rfan1 5 months ago
- return if is_boot_encrypted && !is_leap && !is_sle && !is_leap_micro && !is_sle_micro && !is_alp;
+ return if is_boot_encrypted && !is_leap && !is_sle('<15-sp6') && !is_leap_micro && !is_sle_micro && !is_alp;
yast VR
Staging VR
With the code change, most of the failed cases are passed expect one http://openqa.suse.de/tests/12980462#
The failed case has below crypt settings without LVM, is it by design?
/etc/crypttab
cr_swap UUID=36fa6b83-1104-43c2-956f-c7fb736ee8bd
cr_home UUID=35aeeb35-4cff-4eab-b0de-24ad790db52b
cr_root UUID=0317455a-46cd-477c-a21c-caa50a1481e8 none x-initrd.attach
Updated by rfan1 5 months ago
- Copied to action #152137: [qe-core] Add 'crypt_no_lvm' to staging tests added
Updated by rfan1 5 months ago
rfan1 wrote in #note-13:
- return if is_boot_encrypted && !is_leap && !is_sle && !is_leap_micro && !is_sle_micro && !is_alp; + return if is_boot_encrypted && !is_leap && !is_sle('<15-sp6') && !is_leap_micro && !is_sle_micro && !is_alp;yast VR
Staging VR
With the code change, most of the failed cases are passed expect one http://openqa.suse.de/tests/12980462#The failed case has below crypt settings without
LVM, is it by design?/etc/crypttab cr_swap UUID=36fa6b83-1104-43c2-956f-c7fb736ee8bd cr_home UUID=35aeeb35-4cff-4eab-b0de-24ad790db52b cr_root UUID=0317455a-46cd-477c-a21c-caa50a1481e8 none x-initrd.attach
As discussed with Eugenio Paolantonio, it could be expected result, if we have separate partitions which are encrypted without LVM configuration. we may need to type the passphrase again.
Updated by epaolantonio 5 months ago
Thank you very much for working on this! Re-scheduled run on Staging:C worked fine: https://openqa.suse.de/tests/13062495
Updated by openqa_review 4 months ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: upgrade_Leap_15.0_cryptlvm@uefi
https://openqa.opensuse.org/tests/3810146#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.