action #56774
closedcoordination #56267: [epic][qe-core][functional] openSUSE welcome message is not properly handled
[functional][u] test fails in boot_to_desktop - openSUSE Welcome not handled in upgrade scenarios
Added by StefanBruens over 4 years ago. Updated about 4 years ago.
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-Leap-42.3-gnome@64bit_cirrus fails in
boot_to_desktop
Acceptance criteria¶
- AC1: The "Show on start" checkbox of the opensuse-welcome popup dialog is unticked.
- AC2: opensuse-welcome popup dialog is closed.
- AC3: The change is verified in all upgrade scenario from Leap to Tumbleweed.
Reproducible¶
Fails since (at least) Build 20190909 (current job)
Expected result¶
Last good: 20190907 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by SLindoMansilla over 4 years ago
- Subject changed from test fails in boot_to_desktop - openSUSE Welcome not handled in upgrade scenarios to [functional][u] test fails in boot_to_desktop - openSUSE Welcome not handled in upgrade scenarios
- Parent task set to #56267
Updated by StefanBruens over 4 years ago
- Status changed from New to In Progress
- Assignee set to StefanBruens
Updated by dimstar over 4 years ago
Not sure if you'd prefer a different issue, but I'd think we should collect all those oS-welcome things together.
So, there are some more cases:
The multi-users-dm test creates new users and logs in as a different user. Obviously, oS-welcome is shown (the 'do-no-show from earlier was for the initial user)
LXQt also shows oS-welcome
Updated by StefanBruens over 4 years ago
LXQt is already covered by https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8412
Updated by StefanBruens over 4 years ago
For the multi_users_dm test, see https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8451
Updated by okurz over 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: autoyast_reinstall_gnome
https://openqa.opensuse.org/tests/1052630
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 okurz over 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: autoyast_reinstall_gnome
https://openqa.opensuse.org/tests/1065151
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 StefanBruens over 4 years ago
- Assignee deleted (
StefanBruens)
Updated by SLindoMansilla over 4 years ago
- Status changed from Feedback to Workable
Updated by SLindoMansilla over 4 years ago
- Follows action #55661: [opensuse][u] test fails in several modules after booting and login - "openSUSE Welcome" not handled (WAS: test fails in first_boot) added
Updated by SLindoMansilla over 4 years ago
I think when module first_boot is addressed on create_hdd* scenarios, this will not be necessary.
See #55661
Updated by mgriessmeier about 4 years ago
- Status changed from New to Workable
- Target version set to Milestone 30
- Estimated time set to 42.00 h
ATM there is a workaround with EXCLUDE_MODULES=opensuse_welcome
so let's work on this anytime soon
the goal should be to not have "opensuse_welcome" scheduled, unless explicitely scheduled
Updated by zluo about 4 years ago
- Status changed from Workable to In Progress
- Assignee set to zluo
checking the current status
Updated by zluo about 4 years ago
Updated by zluo about 4 years ago
checked TW, we have actually the only case with opensuse_welcome which makes trouble.
Updated by SLindoMansilla about 4 years ago
All this jobs are scheduling the module opensuse_welcome¶
O3¶
- TW x86_64: https://openqa.opensuse.org/tests/overview?arch=&machine=&modules=opensuse_welcome&distri=microos&distri=opensuse&version=Tumbleweed&build=20200413&groupid=1#
- Leap 15.2 x86_64: https://openqa.opensuse.org/tests/overview?arch=&machine=&modules=opensuse_welcome&distri=opensuse&version=15.2&build=626.2&groupid=50#
OSD¶
- Functional: none found https://openqa.suse.de/tests/overview?arch=&machine=&modules=opensuse_welcome&distri=sle&version=15-SP2&build=176.1&groupid=110#
- Desktop: none found https://openqa.suse.de/tests/overview?arch=&machine=&modules=opensuse_welcome&distri=sle&version=15-SP2&build=176.1&groupid=118#
- Migration: none found https://openqa.suse.de/tests/overview?arch=&machine=&modules=opensuse_welcome&distri=sle&version=15-SP2&build=176.1&groupid=265#
- Yast: none found https://openqa.suse.de/tests/overview?arch=&machine=&modules=opensuse_welcome&distri=sle&version=15-SP2&build=176.1&groupid=129#
Updated by zluo about 4 years ago
will create YAML schedule at https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/schedule/migration
zdup-Leap-42.3-gnome.yaml
add later a setting YAML_SCHEDULE=schedule/migration/zdup-Leap-42.3-gnome.yaml for test suite.
Updated by zluo about 4 years ago
to check later:
Updated by zluo about 4 years ago
YAML_SCHEDULE=schedule/migration/zdup-Leap-42.3-gnome.yaml added in test suite zdup-Leap-42.3-gnome.
check this later on O3 then
Updated by zluo about 4 years ago
- Status changed from In Progress to Resolved
https://openqa.opensuse.org/tests/1243241#settings is there and opensuse_welcome is excluded as expected.