action #16396
closed[sle][functional]'ret' in grub_test is not catched / too late, ending up in encrypt password prompt
0%
Description
Observation¶
openQA test in scenario sle-12-SP3-Server-DVD-x86_64-cryptlvm+activate_existing+force_recompute@64bit fails in
boot_encrypt
because the key 'ret' that should have ended up in the previous test module does not cause the boot menue to directly boot but ends up in the password prompt for the encrypted volume which then switches to the console mode for password entry.
Reproducible¶
Failed once in this Build 0231 (current job)
Expected result¶
Last good: 0230 (or more recent)
Also look at video. The grub screen is detected and the 8 seconds boot timeout is aborted early.
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 7 years ago
- Subject changed from 'ret' in grub_test is not catched / too late, ending up in encrypt password prompt to [sle][functional]'ret' in grub_test is not catched / too late, ending up in encrypt password prompt
Updated by okurz about 6 years ago
- Due date set to 2018-03-13
after recent changes to encrypted unlocking worth to check again.
Updated by okurz about 6 years ago
- Status changed from New to Resolved
- Assignee set to okurz
well, tests seem to be fine regarding the unlocking as well as the check for grub. Since then we have a disabled grub timeout as well as reworked the bootloader handling so I assume we are good.