action #152062
closed[qe-core] test fails in grub_test - the password prompt doesn't not appear but this is uefi (aarch64 only)
0%
Description
Observation¶
It's not like lvm-full-encrypt on x86_64 is running on legacy, on aarch64 this is running on uefi, I suppose the encrypted password prompt will be show at the different stage?
openQA test in scenario opensuse-15.6-DVD-aarch64-lvm-full-encrypt@aarch64 fails in
grub_test
Test suite description¶
poo#15926 (crypt-)LVM installations can take longer, especially on non-x86_64 architectures. Test suite creates encrypted lvm partition using expert partitioner and performs installation.
Reproducible¶
Fails since (at least) Build 521.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by mlin7442 about 1 year ago
and https://openqa.opensuse.org/tests/3781150#step/first_boot/18 seem to be related?
Updated by ggardet_arm about 1 year ago
This test does not exist on Tumbleweed to compare.
The closer one seems to be cryptlvm https://openqa.opensuse.org/tests/3779171 which does not show password prompt on grub.
Updated by maritawerner about 1 year ago
- Subject changed from test fails in grub_test - the password prompt doesn't not appear but this is uefi (aarch64 only) to [qe-core] test fails in grub_test - the password prompt doesn't not appear but this is uefi (aarch64 only)
Updated by szarate about 1 year ago
- Sprint set to QE-Core: December Sprint 23 (Dec 13 - Jan 10)
- Tags set to qe-core-december-sprint
- Status changed from New to Workable
- Assignee set to rfan1
- Target version set to QE-Core: Ready
Updated by rfan1 about 1 year ago · Edited
@mlin7442, I can see the job setting below:
- lvm-full-encrypt:
settings:
YAML_TEST_DATA: test_data/yast/encryption/lvm_encrypt_separate_boot_uefi.yaml
Is separate_boot expected for this test? thanks
IMO, we don't need separate boot partition if we set full disk encryption.
Updated by rfan1 about 1 year ago
The issue is gone after adding setting UNENCRYPTED_BOOT=1
https://openqa.opensuse.org/tests/3821463#settings
Updated by rfan1 about 1 year ago · Edited
- Status changed from Workable to In Progress
Then 2 issues need to be fix in this case:
We need to make sure /boot partition is managed by LVM and is encrypted, see x86_64 job https://openqa.opensuse.org/tests/3809944#step/new_partitioning_gpt/4
We may need to fix the libyui test code to handle UEFI
Updated by rfan1 about 1 year ago · Edited
Well, I can get the right configuration file now:
YAML_TEST_DATA=test_data/yast/encryption/full_lvm_enc_uefi.yaml
However, new issue is seen https://openqa.opensuse.org/tests/3822472#step/first_boot/22
With full disk encryption + lvm, it requires the passphrase again after grub. seems aarch64 specific issue, I will double check with developer.
Updated by rfan1 about 1 year ago
The issue seem only be seen with opensuse [leap or tw] + aarch64 platform. which is tracked via bug https://bugzilla.opensuse.org/show_bug.cgi?id=1205314
Let me mark it as blocked before developer's feedback
Updated by rfan1 about 1 year ago
- Status changed from Blocked to In Progress
I can get dev's kindly feedback, the new issue is caused by job setting GRUB_KERNEL_OPTION_APPEND
Once we change the grub setting, we need to type the passphrase again, it is by design.
Re-run the failed jobs with GRUB_KERNEL_OPTION_APPEND=''
https://openqa.opensuse.org/tests/overview?distri=opensuse&build=rfan1219_o3new
Updated by rfan1 about 1 year ago
One more setting is wrong in https://openqa.opensuse.org/tests/3810069#step/first_boot/18
YAML_TEST_DATA test_data/yast/encryption/lvm_encrypt_separate_boot_uefi.yaml
Updated by rfan1 about 1 year ago
Updated by rfan1 about 1 year ago
Updated by rfan1 about 1 year ago
- Status changed from In Progress to Feedback
PR is merged, wait for openQA test results.
Updated by openqa_review 12 months ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: lvm-full-encrypt
https://openqa.opensuse.org/tests/3810068#step/grub_test/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 12 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: lvm_thin_provisioning
https://openqa.opensuse.org/tests/3873863#step/first_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.