action #152621
closed[qe-core]test fails in boot_encrypt
Added by dimstar 5 months ago. Updated 5 months ago.
0%
Description
Observation¶
The PR for new decrypt logic has been merged, which in turn resulted in this new test failure
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-create_hdd_gnome_encrypt_separate_boot@64bit fails in
boot_encrypt
Test suite description¶
Maintainer: (Richard Fan) richard.fan@suse.com (Starry Wang) starry.wang@suse.com
Reproducible¶
Fails since (at least) Build 20231213
Expected result¶
Last good: 20231212 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by rfan1 5 months ago · Edited
- I think the best way is un-schedule the test module
For below cases:
https://openqa.opensuse.org/tests/3812286#step/boot_encrypt/1
https://openqa.opensuse.org/tests/3812284#step/boot_encrypt/1
- I will try with adding
LVM=1
Updated by mlin7442 5 months ago
Two fails on Leap 15 group:
crypt_no_lvm https://openqa.opensuse.org/tests/3809925 - it has passpharse prompt for root partition still
all upgrade_cryptlvm scenarios still has boot_encrypt step but there is no passpharse prompt eg. https://openqa.opensuse.org/tests/3809928 , this one should be the same cause as the Tumbleweed fail on leap15_to_tumbleweed upgrade scenario.
Updated by rfan1 5 months ago
mlin7442 wrote in #note-6:
Two fails on Leap 15 group:
crypt_no_lvm https://openqa.opensuse.org/tests/3809925 - it has passpharse prompt for root partition still
The settingFULL_LVM_ENCRYPT=1seems wrong, will try to remove it.all upgrade_cryptlvm scenarios still has boot_encrypt step but there is no passpharse prompt eg. https://openqa.opensuse.org/tests/3809928 , this one should be the same cause as the Tumbleweed fail on leap15_to_tumbleweed upgrade scenario.
Will test with setting LVM=1
Updated by rfan1 5 months ago
rfan1 wrote in #note-7:
mlin7442 wrote in #note-6:
Two fails on Leap 15 group:
crypt_no_lvm https://openqa.opensuse.org/tests/3809925 - it has passpharse prompt for root partition still
The settingFULL_LVM_ENCRYPT=1seems wrong, will try to remove it.
The new test passed at grub phase, investigating: https://openqa.opensuse.org/tests/3812629#step/grub_test/3all upgrade_cryptlvm scenarios still has boot_encrypt step but there is no passpharse prompt eg. https://openqa.opensuse.org/tests/3809928 , this one should be the same cause as the Tumbleweed fail on leap15_to_tumbleweed upgrade scenario.
Will test with setting LVM=1
Added LVM=1 to test_suiteupgrade_Leap_15.4_cryptlvm
Updated by rfan1 5 months ago
rfan1 wrote in #note-8:
rfan1 wrote in #note-7:
mlin7442 wrote in #note-6:
Two fails on Leap 15 group:
- crypt_no_lvm https://openqa.opensuse.org/tests/3809925 - it has passpharse prompt for root partition still The setting
FULL_LVM_ENCRYPT=1seems wrong, will try to remove it. The new test passed at grub phase, investigating: https://openqa.opensuse.org/tests/3812629#step/grub_test/3I can find the root cause now, it is caused by
STORAGE_NGnot set, now it is passed withSTORAGE_NG=1
Modify the test suite then
- all upgrade_cryptlvm scenarios still has boot_encrypt step but there is no passpharse prompt eg. https://openqa.opensuse.org/tests/3809928 , this one should be the same cause as the Tumbleweed fail on leap15_to_tumbleweed upgrade scenario.
Will test with setting LVM=1
Added LVM=1 to test_suiteupgrade_Leap_15.4_cryptlvm
Updated by dimstar 5 months ago
rfan1 wrote in #note-3:
- I think the best way is un-schedule the test module
For below cases:
https://openqa.opensuse.org/tests/3812286#step/boot_encrypt/1
https://openqa.opensuse.org/tests/3812284#step/boot_encrypt/1
- I will try with adding
LVM=1
Interesting - one of them works, the other had the same error as before the PR merge
- https://openqa.opensuse.org/tests/3812389 (clone of 3812284) => failed
- https://openqa.opensuse.org/tests/3812448 (clone of 3812286) => passed
Updated by rfan1 5 months ago
dimstar wrote in #note-10:
rfan1 wrote in #note-3:
- I think the best way is un-schedule the test module
For below cases:
https://openqa.opensuse.org/tests/3812286#step/boot_encrypt/1
https://openqa.opensuse.org/tests/3812284#step/boot_encrypt/1
- I will try with adding
LVM=1Interesting - one of them works, the other had the same error as before the PR merge
- https://openqa.opensuse.org/tests/3812389 (clone of 3812284) => failed
- https://openqa.opensuse.org/tests/3812448 (clone of 3812286) => passed
https://openqa.opensuse.org/tests/3812389#step/reboot_gnome/9 seems like needle issue
Updated by dimstar 5 months ago
- Status changed from Resolved to In Progress
There is one case left for boot_encrypt failures: https://openqa.opensuse.org/tests/3822778#step/boot_encrypt/12
Updated by rfan1 5 months ago
- Status changed from In Progress to Feedback
dimstar wrote in #note-13:
There is one case left for boot_encrypt failures: https://openqa.opensuse.org/tests/3822778#step/boot_encrypt/12
Hello @dimstar, as we discussed in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18270
This test scenario should not a right one and need to be un-scheduled.
So, can we file a new ticket to qe-security team and close this one?
Updated by dimstar 5 months ago
rfan1 wrote in #note-14:
dimstar wrote in #note-13:
There is one case left for boot_encrypt failures: https://openqa.opensuse.org/tests/3822778#step/boot_encrypt/12
Hello @dimstar, as we discussed in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18270
This test scenario should not a right one and need to be un-scheduled.So, can we file a new ticket to qe-security team and close this one?
Fine - let's keep https://progress.opensuse.org/issues/120459 around for this (maybe, someday)
Updated by rfan1 5 months ago
dimstar wrote in #note-15:
rfan1 wrote in #note-14:
dimstar wrote in #note-13:
There is one case left for boot_encrypt failures: https://openqa.opensuse.org/tests/3822778#step/boot_encrypt/12
Hello @dimstar, as we discussed in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18270
This test scenario should not a right one and need to be un-scheduled.So, can we file a new ticket to qe-security team and close this one?
Fine - let's keep https://progress.opensuse.org/issues/120459 around for this (maybe, someday)
Thanks much!