action #60992
closed[qe-core][functional][sporadic] generic problem with select_console / workqueue lockup message
Added by StefanBruens almost 5 years ago. Updated about 4 years ago.
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-NET-x86_64-upgrade_Leap_42.3_cryptlvm@uefi fails in
curl_https
select_console 'user-console' works as expected, but stumbles over the common 'workqueue lockup' kernel error message.
The message should be detected (there are already needles for it), then a send_key 'ret' should be suficient to get a prompt on a new line.
Tasks¶
- Check if the workqueue lockup message is shown with a workaround needle match, then press enter.
- Continue to "select console"
Reproducible¶
Fails since (at least) Build 20191211 (current job)
Expected result¶
Last good: 20191210 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by mgriessmeier almost 5 years ago
- Category changed from Refactor/Code Improvements to Enhancement to existing tests
Updated by mgriessmeier almost 5 years ago
- Subject changed from generic problem with select_console / workqueue lockup message to [functional][u] generic problem with select_console / workqueue lockup message
- Priority changed from Normal to High
Updated by SLindoMansilla almost 5 years ago
- Subject changed from [functional][u] generic problem with select_console / workqueue lockup message to [functional][u][sporadic] generic problem with select_console / workqueue lockup message
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 28
- Estimated time set to 42.00 h
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 28 to Milestone 30
moving to current Milestone
Updated by zluo almost 5 years ago
- Status changed from Workable to In Progress
- Assignee set to zluo
take over.
Updated by zluo almost 5 years ago
Updated by zluo almost 5 years ago
PR updated now
create also a new workaround needle with different tag than current workaround "root-console":
https://github.com/Zaoliang/os-autoinst-needles-opensuse/pull/new/workaround_lockup_message
Updated by zluo almost 5 years ago
https://openqa.opensuse.org/tests/1149222#live
check this later
Updated by zluo almost 5 years ago
https://openqa.opensuse.org/tests/1149288#step/orphaned_packages_check/1
shows workaround is in place.
Updated by zluo almost 5 years ago
- Status changed from In Progress to Rejected
I checked this again and as okurz already pointed out that the code change is not proved. Since this issue is already covered by workaround issue. I'll close this PR and reject the ticket, thanks
Updated by StefanBruens almost 5 years ago
- Status changed from Rejected to Workable
You should not close this - the issue is valid.
There is one instance where the issue is already covered, this just leaves every other instance ..
Updated by okurz almost 5 years ago
@zluo the issue is not already covered by a needle that just detects the situation. Please read my suggestion in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9320#issuecomment-576528575 carefully again.
Updated by SLindoMansilla almost 5 years ago
- Status changed from Workable to New
- Assignee deleted (
zluo)
It needs a team consensus.
Updated by SLindoMansilla almost 5 years ago
The bug is properly marked as soft-fail: https://openqa.opensuse.org/tests/1149288#step/orphaned_packages_check/3
due to
commit 941cab6d37f03bc99b890de04d0a4ad8166fb09c (dheidler/soft)
Author: Dominik Heidler <dheidler@suse.de>
Date: Mon Mar 18 13:14:48 2019 +0100
Consider "rogue workqueue lockup" error as soft
diff --git a/lib/known_bugs.pm b/lib/known_bugs.pm
index 07d865647..b81979e05 100644
--- a/lib/known_bugs.pm
+++ b/lib/known_bugs.pm
@@ -33,7 +33,7 @@ sub create_list_of_serial_failures {
# Detect rogue workqueue lockup
- push @$serial_failures, {type => 'hard', message => 'rogue workqueue lockup bsc#1126782', pattern => quotemeta 'BUG: workqueue lockup'};
+ push @$serial_failures, {type => 'soft', message => 'rogue workqueue lockup bsc#1126782', pattern => quotemeta 'BUG: workqueue lockup'};
# Detect bsc#1093797 on aarch64
if (is_sle('=12-SP4') && check_var('ARCH', 'aarch64')) {
But, the workaround of pressing ret key is not yet implemented.
This test worked because it typed the command before checking the console.
Updated by zluo almost 5 years ago
- Status changed from New to Workable
set it as workable because we have discussed this issue already.
Updated by zluo almost 5 years ago
- Blocks action #44156: [opensuse][functional][u][sporadic][ppc64le] test fails in yast2_lan because rcu message in user-console added
Updated by dheidler almost 5 years ago
I'm not 100% sure what should be done here.
The linked fail only happened once and didn't appear anymore in the last two months.
So I guess it would not really make sence to fix the curl_https module.
So is the idea here to change the code in select_console?
Updated by okurz almost 5 years ago
Updated by jorauch over 4 years ago
- Status changed from Workable to In Progress
- Assignee set to jorauch
Lets see if the new tasks will fix this
Updated by szarate about 4 years ago
- Related to action #46988: [qe-core][functional] Detect known bugs from system journal added
Updated by zluo about 4 years ago
- Blocks deleted (action #44156: [opensuse][functional][u][sporadic][ppc64le] test fails in yast2_lan because rcu message in user-console)
Updated by szarate about 4 years ago
- Status changed from In Progress to Workable
Updated by jorauch about 4 years ago
- Status changed from In Progress to Feedback
Created PR:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11267
Needs tidy
Updated by szarate about 4 years ago
- Status changed from Feedback to In Progress
Updated by tjyrinki_suse about 4 years ago
- Subject changed from [functional][u][sporadic] generic problem with select_console / workqueue lockup message to [qe-core][functional][sporadic] generic problem with select_console / workqueue lockup message
Updated by jorauch about 4 years ago
- Status changed from In Progress to Resolved
PR is merged and no one complained, considering this as resolved