action #155248
open[security][15-SP6] logic of passphrase entering failed in autoyast_stig_remediation
0%
Description
openQA test in scenario sle-15-SP6-Online-x86_64-autoyast_stig_remediation@64bit fails in
first_boot
It started in Build 45.1
While it was still working in 44.1 - over there the "boot_encrypt" module entered the passphrase, while now in boot_encrypt module it's still showing the grub authentication and thein fails in first_boot
If looking at the videos, even on 45.1 it does enter the grub passphrase, but then maybe (possibly, not necessarily) due to ticket #152455 expects that it would be enough, while in this stig case it does not seem the pass-through is working anymore? Not sure why though, the password is the same but maybe it's part of stig logic to not allow pass-through?
Further details¶
Always latest result in this scenario: latest
Automatic re-runs indicate git commit f69e77d29d96cab7c9a3e18c5cd2cfb73f371ee4 (from the time 44.1 build was done) still works for this test suite (https://openqa.suse.de/tests/13457092#comments).
Updated by tjyrinki_suse 3 months ago
- Subject changed from [security] logic of passphrase entering failed in autoyast_stig_remediation to [security][15-SP6] logic of passphrase entering failed in autoyast_stig_remediation
Updated by tjyrinki_suse 2 months ago
See the duplicate for another example - the boot_encrypt code changes ("New logic to type LUKS passphrase in grub phase", "Rename need_passphrase_again to need_unlock_after_bootloader" somehow, while probably a good idea in general, miss support for these cases.
Updated by emiler 2 months ago
Still present in a new build 57.1: https://openqa.suse.de/tests/13548437#step/krb5_crypt_nfs_server/12
Updated by openqa_review about 2 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: autoyast_stig_remediation
https://openqa.suse.de/tests/13646687#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.
Updated by openqa_review 15 days ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: autoyast_stig_remediation
https://openqa.suse.de/tests/13913885#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 68 days if nothing changes in this ticket.