action #170098
open[qe-core] test fails in trup_smoke
0%
Description
Observation¶
This test failed 7 times (the link below is the try number 7) before working https://openqa.opensuse.org/tests/4656298
Could you please take a look? This can often block staging since the test needs to be re-run many times and when it works after so many tries you still wonder of the result or how useful is the test
openQA test in scenario microos-Staging:D-Staging-MicroOS-Image-sdboot-x86_64-microos-wizard-tpm@uefi-staging fails in
trup_smoke
Test suite description¶
Like MicroOS, but use neither combustion nor ignition for the intial configuration, so jeos-firstboot runs.
Reproducible¶
Fails since (at least) Build D.84.1 (current job)
Expected result¶
Last good: D.83.8 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by jlausuch about 2 months ago
Has there been any recent update in Disk Encryption feature? That would explain it...
Updated by anag about 2 months ago
Another example, https://openqa.opensuse.org/tests/4656355 worked after 2 fails
Updated by szarate about 2 months ago
- Tags set to bugbusters
- Subject changed from test fails in trup_smoke to [qe-core] test fails in trup_smoke
- Target version set to QE-Core: Ready
Updated by jlausuch about 2 months ago
Change that caused the issue https://build.opensuse.org/package/revisions/openSUSE:Factory/disk-encryption-tool
The test code needs adaptation to this change.
Updated by mgrifalconi about 1 month ago
jlausuch wrote in #note-4:
Change that caused the issue https://build.opensuse.org/package/revisions/openSUSE:Factory/disk-encryption-tool
The test code needs adaptation to this change.
Hello @jlausuch can you please give some more info, I see a list of changes but it does not explain why once ever 5-6 runs, it is successful and in the failures a password is requested.
What should be changed in the test and why is it now inconsistent?
Also, the test is set to immediately soft-fail if FLAVOR contains "encrypted" keyword (which is not the case), but ENCRYPT is set to 1 and the disk is being encrypted during first boot so I am a little confused.
Thanks!