action #55832
closed
[functional][u] test fails in first_boot - default boot scenario in spvm ends up in a console
Added by szarate over 4 years ago.
Updated almost 4 years ago.
Category:
Bugs in existing tests
Description
Observation¶
The default scenario doesn't have DESKTOP variable set, so the system doesn't match anything, and test fails, even if the installation was correct, We should define what should happen in these cases.
Do we want to test that we have gnome available on SPVM? Also the SUT doesn't seem to have a display that X can use.
openQA test in scenario sle-12-SP5-Server-DVD-ppc64le-default@ppc64le-spvm fails in
first_boot
Test suite description¶
Maintainer: okurz
The standard scenario where we mainly just follow installation suggestions without any adjustments.
Reproducible¶
Fails since (at least) Build 0259
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Files
Related issues
1 (1 open — 0 closed)
- Subject changed from test fails in first_boot - default boot scenario in spvm ends up in a console to [functional][u] test fails in first_boot - default boot scenario in spvm ends up in a console
- Status changed from New to Feedback
- Assignee set to mgriessmeier
@Matze can you clarify here what's expected?
- Related to coordination #53249: [epic][qe-core][functional] ensure that grub_test gets a booting system added
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: default@ppc64le-spvm
https://openqa.suse.de/tests/3613493
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"
- The label in the openQA scenario is removed
- Status changed from Feedback to Resolved
Also available in: Atom
PDF