action #62735
closed[functional][u] test fails in boot_to_desktop - Test expects textmode, but GNOME is present
0%
Description
Observation¶
Before SLE15-SP2, there was only one installer media. The user could skip the registration and then minimal system role was forced to be used.
This scenario was covering the behavior of that minimal system registering against SCC.
Since SLE15-SP2, there are two installer media, Full medium and Online medium. Full medium is the only one that allows skipping registration, but it allows to select other system roles like textmode or GNOME.
With the Full media, a user would not ever install a minimal role system, but textmode or GNOME, it is not worth to cover that scenarios. So, post-registration should cover any of those. Since there is already a skip_registration scenario using the GNOME role, minimal+proxy_SCC-postreg_SUSEconnect needs to be adapted to use DESKTOP=gnome
Reproducible¶
- In scenario sle-15-SP2-Online-aarch64-minimal+proxy_SCC-postreg_SUSEconnect@aarch64
- Fails since Build 128.1
- And in scenario sle-15-SP2-Online-ppc64le-Build128.1-sergio-minimal+proxy_SCC-postreg_SUSEconnect@ppc64le
- Fails since Build 128.1
Expected result¶
- It never worked since new media
- Last good from SLE15-SP1: 228.2
Further details¶
Latest result¶
Updated by okurz about 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: minimal+proxy_SCC-postreg_SUSEconnect
https://openqa.suse.de/tests/3869659
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
Updated by SLindoMansilla about 4 years ago
- Status changed from New to In Progress
- Assignee set to SLindoMansilla
- Target version set to Milestone 30
The setting DESKTOP=gnome solves the problem for module boot_to_desktop.
suseconnect_scc needs a select_console
Updated by SLindoMansilla about 4 years ago
DESKTOP=gnome is now set for minimal+proxy_SCC-postreg_SUSEconnect in https://openqa.suse.de/admin/test_suites
Updated by SLindoMansilla about 4 years ago
Updated by SLindoMansilla about 4 years ago
- Status changed from In Progress to Resolved
Verified on OSD: https://openqa.suse.de/tests/3902116
Updated by okurz about 4 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: minimal+proxy_SCC-postreg_SUSEconnect
https://openqa.suse.de/tests/4101542
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
Updated by oorlov about 4 years ago
I have fixed the issue by passing ADDONS: all-packages in Test Suite settings instead of YAML for skip_registration test suite.
Passed Jobs for minimal+proxy_SCC-postreg_SUSEconnect:
x64: https://openqa.suse.de/tests/4106887
ppc64le: https://openqa.suse.de/tests/4107300
Unfortunately I cannot provide the VR for aarch64, as shutdown module in skip_registration is failed due to https://bugzilla.suse.com/show_bug.cgi?id=1166397, so that qcow is not published.
Updated by SLindoMansilla about 4 years ago
oorlov wrote:
I have fixed the issue by passing ADDONS: all-packages in Test Suite settings instead of YAML for skip_registration test suite.
Passed Jobs for minimal+proxy_SCC-postreg_SUSEconnect:
x64: https://openqa.suse.de/tests/4106887
ppc64le: https://openqa.suse.de/tests/4107300Unfortunately I cannot provide the VR for aarch64, as shutdown module in skip_registration is failed due to https://bugzilla.suse.com/show_bug.cgi?id=1166397, so that qcow is not published.
Thanks! :)