action #179020
closed[core][powerVM]test fails in NET-BOOT bootloader due to ask for root password for encrypted disk
0%
Description
Description¶
This is not the first time we hit this sporadic issue on powerVM setups.
Net boot failed and got stuck at asking for password root disk. we tried some workaround before like SET_NVRAM_DEFAULTS=1
, but didn't fix the problem.
I can't tell the stable reproduce steps, but seems it happens more after sle16 installation with root disk encrypted.
I tried some workaround which is mentioned in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/21407 however I don't think it is a perfect solution.
Please see https://suse.slack.com/archives/C02CLB2LB7Z/p1742210735779749 for more detailed information. maybe tools team has perfect solution for this.
Thanks,
Richard.
Observation¶
openQA test in scenario sle-16.0-Online-ppc64le-create_hdd_textmode@tinawang123/os-autoinst-distri-opensuse#ssh@ppc64le-hmc-single-disk fails in
bootloader
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build tinawang123/os-autoinst-distri-opensuse#ssh (current job)
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by JERiveraMoya 3 months ago
It is sporadic in the sense that happens if the reused lpar has previously installed a sle 16 system encrypted, using the same lpar and running and encrypted scenario previously should be 100% reproducible and it is expected that one of the two passphrase will be prompted before grub.
Updated by okurz 3 months ago
- Project changed from openQA Infrastructure (public) to openQA Tests (public)
- Subject changed from [tools][powerVM]test fails in NET-BOOT bootloader due to ask for root password for encrypted disk to [core][powerVM]test fails in NET-BOOT bootloader due to ask for root password for encrypted disk
- Category set to Bugs in existing tests
- Target version set to future
Sorry, I don't see how we can help here. The issue does not ring a bell