action #109692
closed
[sle][migration][sle15sp4]test fails in boot_to_desktop - not a bootable device
Added by tinawang123 about 2 years ago.
Updated about 2 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP4-Migration-from-SLE12-SPx-ppc64le-offline_sles12sp3_ltss_media_base_def_full@ppc64le fails in
boot_to_desktop
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 124.1 (current job)
Expected result¶
Last good: 119.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Estimated time set to 16.00 h
lpalovsky wrote:
It probably fixes https://bugzilla.suse.com/show_bug.cgi?id=1198205 too.
Not sure what was the purpose of this new rng device.
Hardware machines have an rng, so we would like to be as close as possible in testing.
Also on aarch64 there are KASLR related errors (KASLR doesn't work without rng there) without RNG.
dheidler wrote:
lpalovsky wrote:
It probably fixes https://bugzilla.suse.com/show_bug.cgi?id=1198205 too.
Not sure what was the purpose of this new rng device.
Hardware machines have an rng, so we would like to be as close as possible in testing.
Also on aarch64 there are KASLR related errors (KASLR doesn't work without rng there) without RNG.
Yes, I agree. It's good to have it covered. The issue here is a new device being added to the configuration. For most of the scenarios this is ok but migration tests are using pre-installed qcows which are then migrated to the target version. This new device then causes naming shift and results in various failures:
- power machines trying to boot incorrect device - This can be fixed with test code in PR @tinawang123 proposed. The code was using a static value so it's good to improve it anyway.However this will still lead to the second issue.
- during migration, yast starts to complain about boot devices and this affects all HA power and x86 based scenarios.
https://openqa.suse.de/tests/8495019#step/start_install/2
This is harder to fix. You either need to re-create all source qcow images with new rng device included, or adding a function to the testcode which would proceed in the migration.
Disabling rng device in yaml only for affected scenarios and architectures seems like a good compromise.
- Status changed from New to Resolved
- % Done changed from 0 to 100
Also available in: Atom
PDF