Project

General

Profile

Actions
Copy link

action #64042

closed

[qe-core][functional][sporadic] test fails in NM_wpa2_enterprise: "dhcp4 (wlan1): request timed out" Leap15.2 ppc64le

Added by michel_mno about 4 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
zluo
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 30
Start date:
2020-03-02
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

As per journalctl extract, seems to have a timing issue that make the wlan activation to fail.

extract journalctl: https://openqa.opensuse.org/tests/1191824/file/NM_wpa2_enterprise-journal.log

Mar 01 02:20:19 susetest kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Mar 01 02:20:19 susetest NetworkManager[3168]: <info>  [1583047219.8364] device (wlan1): supplicant interface state: associated -> completed
Mar 01 02:20:19 susetest NetworkManager[3168]: <info>  [1583047219.8364] device (wlan1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "foobar"
Mar 01 02:20:19 susetest NetworkManager[3168]: <info>  [1583047219.8365] device (p2p-dev-wlan1): supplicant management interface state: associated -> completed
Mar 01 02:20:19 susetest NetworkManager[3168]: <info>  [1583047219.8714] device (wlan1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 01 02:20:19 susetest NetworkManager[3168]: <info>  [1583047219.8719] dhcp4 (wlan1): activation: beginning transaction (timeout in 45 seconds)
Mar 01 02:20:19 susetest avahi-daemon[953]: Joining mDNS multicast group on interface wlan1.IPv6 with address fe80::f270:84c:a7c5:2604.
Mar 01 02:20:19 susetest avahi-daemon[953]: New relevant interface wlan1.IPv6 for mDNS.
Mar 01 02:20:19 susetest avahi-daemon[953]: Registering new address record for fe80::f270:84c:a7c5:2604 on wlan1.*.
Mar 01 02:20:24 susetest systemd[1334]: Started Application launched by gnome-shell.
Mar 01 02:20:34 susetest su[3458]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Mar 01 02:20:34 susetest su[3458]: gkr-pam: couldn't unlock the login keyring.
Mar 01 02:20:34 susetest su[3458]: (to root) bernhard on pts/0
Mar 01 02:20:35 susetest su[3458]: pam_unix(su:session): session opened for user root by bernhard(uid=1000)
Mar 01 02:21:05 susetest NetworkManager[3168]: <warn>  [1583047265.5070] dhcp4 (wlan1): request timed out
Mar 01 02:21:05 susetest NetworkManager[3168]: <info>  [1583047265.5072] dhcp4 (wlan1): state changed unknown -> timeout
Mar 01 02:21:05 susetest NetworkManager[3168]: <info>  [1583047265.5074] dhcp4 (wlan1): canceled DHCP transaction
Mar 01 02:21:05 susetest NetworkManager[3168]: <info>  [1583047265.5074] dhcp4 (wlan1): state changed timeout -> done
Mar 01 02:21:05 susetest NetworkManager[3168]: <info>  [1583047265.5078] device (wlan1): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Mar 01 02:21:05 susetest NetworkManager[3168]: <warn>  [1583047265.5100] device (wlan1): Activation: failed for connection 'foobar'
Mar 01 02:21:05 susetest kernel: wlan1: deauthenticating from be:86:91:4d:82:32 by local choice (Reason: 3=DEAUTH_LEAVING)

Some logs difference after connection_uuid.

Broken:

[ 1580.153779] NetworkManager[3974]: <warn>  [1591164299.7843] sup-iface[0xaaaaeadb8110,wlan1]: connection disconnected (reason -3)
[ 1580.155855] NetworkManager[3974]: <info>  [1591164299.7850] device (wlan1): supplicant interface state: completed -> scanning
[ 1580.157839] NetworkManager[3974]: <info>  [1591164299.7850] device (p2p-dev-wlan1): supplicant management interface state: completed -> scanning
[ 1584.157562] NetworkManager[3974]: <info>  [1591164303.8502] device (wlan1): supplicant interface state: scanning -> disconnected
[ 1584.159879] NetworkManager[3974]: <info>  [1591164303.8503] device (p2p-dev-wlan1): supplicant management interface state: scanning -> disconnected

Working:

[ 1624.224134] NetworkManager[3935]: <warn>  [1590759093.7651] sup-iface[0xaaaab9670910,wlan1]: connection disconnected (reason -3)
[ 1624.232670] NetworkManager[3935]: <info>  [1590759093.7673] device (wlan1): supplicant interface state: completed -> disabled
[ 1624.249780] NetworkManager[3935]: <info>  [1590759093.7674] device (p2p-dev-wlan1): supplicant management interface state: completed -> disabled
[ 1624.253398] NetworkManager[3935]: <info>  [1590759093.7678] device (wlan1): supplicant interface state: disabled -> inactive
[ 1624.261844] NetworkManager[3935]: <info>  [1590759093.7681] device (p2p-dev-wlan1): supplicant management interface state: disabled -> inactive
38c0h-0-

Acceptance criteria

  • AC: The test module NM_wpa2_enterprise passes or fail in a product bug.

Exit criteria

  • AC: The test module is unscheduled for ppc

Tasks

  1. Confirm with openSUSE if it makes sense to test network manager on PPC. If not, unschedule test module for PPC.
  2. If it makes sense: Figure out how the WIFI setup is done for that test.
  3. Find possible week points of that setup that could be causing those timeouts. 4a. Fix the setup or adapt the test module to retry WIFI connection. 4b. Or file a product bug

Reproducible

Related issues 3 (0 open — 3 closed)

Has duplicate openQA Tests - action #64505: test fails in NM_wpa2_enterprise - connection failedRejectedSLindoMansilla2020-03-16

Actions
Has duplicate openQA Tests - action #64625: [sporadic] test fails in NM_wpa2_enterprise - Fail to connectRejectedSLindoMansilla2020-03-19

Actions
Has duplicate openQA Tests - action #52952: [aarch64] test fails in NM_wpa2_enterpriseRejectedSLindoMansilla2019-06-12

Actions
Actions
Copy link
 #1

Updated by mgriessmeier about 4 years ago

  • Subject changed from test fails in NM_wpa2_enterprise: "dhcp4 (wlan1): request timed out" Leap15.2 ppc64le to [functional][u] test fails in NM_wpa2_enterprise: "dhcp4 (wlan1): request timed out" Leap15.2 ppc64le
Actions
Copy link
 #2

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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1205758

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #3

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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1219649

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #4

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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1238019

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #5

Updated by okurz almost 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1256121

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #6

Updated by okurz almost 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1272646

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #7

Updated by okurz almost 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1289959

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #8

Updated by okurz almost 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1311753

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #9

Updated by SLindoMansilla almost 4 years ago

  • Subject changed from [functional][u] test fails in NM_wpa2_enterprise: "dhcp4 (wlan1): request timed out" Leap15.2 ppc64le to [functional][u][sporadic] test fails in NM_wpa2_enterprise: "dhcp4 (wlan1): request timed out" Leap15.2 ppc64le
Actions
Copy link
 #10

Updated by SLindoMansilla almost 4 years ago

  • Description updated (diff)
Actions
Copy link
 #11

Updated by SLindoMansilla over 3 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Target version set to Milestone 30
  • Estimated time set to 42.00 h
Actions
Copy link
 #12

Updated by SLindoMansilla over 3 years ago

  • Has duplicate action #64505: test fails in NM_wpa2_enterprise - connection failed added
Actions
Copy link
 #13

Updated by SLindoMansilla over 3 years ago

  • Has duplicate action #64625: [sporadic] test fails in NM_wpa2_enterprise - Fail to connect added
Actions
Copy link
 #14

Updated by SLindoMansilla over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #15

Updated by SLindoMansilla over 3 years ago

  • Has duplicate action #52952: [aarch64] test fails in NM_wpa2_enterprise added
Actions
Copy link
 #16

Updated by michel_mno over 3 years ago

Seems to have similar external problem on Jump (Build71.2) : wlan not activated,
even if trace differ from above reported one.
Do I have to create a new issue ?

extract of NM_wpa2_enterprise-journal.log from jobid#1378949

NetworkManager[3930]: <info>  [1598904614.8391] device (wlan1): supplicant interface state: scanning -> authenticating
NetworkManager[3930]: <info>  [1598904614.8392] device (p2p-dev-wlan1): supplicant management interface state: scanning -> authenticating
kernel: wlan1: aborting authentication with 6e:2b:2a:e1:a5:f9 by local choice (Reason: 3=DEAUTH_LEAVING)
NetworkManager[3930]: <info>  [1598904619.8389] device (wlan1): supplicant interface state: authenticating -> disconnected
NetworkManager[3930]: <info>  [1598904619.8389] device (p2p-dev-wlan1): supplicant management interface state: authenticating -> disconnected
NetworkManager[3930]: <info>  [1598904620.8383] device (wlan1): supplicant interface state: disconnected -> scanning
NetworkManager[3930]: <info>  [1598904620.8384] device (p2p-dev-wlan1): supplicant management interface state: disconnected -> scanning
hostapd[4108]: wlan0: STA 56:b3:96:89:6d:6a IEEE 802.11: authenticated
hostapd[4108]: wlan0: STA 56:b3:96:89:6d:6a IEEE 802.11: authenticated
kernel: wlan1: authenticate with 6e:2b:2a:e1:a5:f9
kernel: wlan1: send auth to 6e:2b:2a:e1:a5:f9 (try 1/3)
kernel: wlan1: authenticated
NetworkManager[3930]: <info>  [1598904624.5688] device (wlan1): supplicant interface state: scanning -> authenticating
NetworkManager[3930]: <info>  [1598904624.5689] device (p2p-dev-wlan1): supplicant management interface state: scanning -> authenticating
kernel: wlan1: aborting authentication with 6e:2b:2a:e1:a5:f9 by local choice (Reason: 3=DEAUTH_LEAVING)
NetworkManager[3930]: <info>  [1598904629.5685] device (wlan1): supplicant interface state: authenticating -> disconnected
NetworkManager[3930]: <info>  [1598904629.5685] device (p2p-dev-wlan1): supplicant management interface state: authenticating -> disconnected
NetworkManager[3930]: <warn>  [1598904630.6928] device (wlan1): Activation: (wifi) association took too long, failing activation
NetworkManager[3930]: <info>  [1598904630.6928] device (wlan1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
NetworkManager[3930]: <warn>  [1598904630.6943] device (wlan1): Activation: failed for connection 'foobar'
NetworkManager[3930]: <info>  [1598904630.6945] device (wlan1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Actions
Copy link
 #17

Updated by okurz over 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1393111

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #18

Updated by okurz over 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1414881

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #19

Updated by okurz over 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1433934

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #20

Updated by okurz over 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1451996

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #21

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [functional][u][sporadic] test fails in NM_wpa2_enterprise: "dhcp4 (wlan1): request timed out" Leap15.2 ppc64le to [qe-core][functional][sporadic] test fails in NM_wpa2_enterprise: "dhcp4 (wlan1): request timed out" Leap15.2 ppc64le
Actions
Copy link
 #22

Updated by okurz over 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1317724

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #23

Updated by okurz over 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1317724

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #24

Updated by zluo over 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to zluo

let me check this issue for now.

Actions
Copy link
 #25

Updated by zluo over 3 years ago

Actions
Copy link
 #26

Updated by zluo over 3 years ago

https://openqa.opensuse.org/tests/1317086 onppc64le looks as well for released leap 15.2

So I need to reproduce this sporadic issue at first.

Actions
Copy link
 #27

Updated by zluo over 3 years ago

https://openqa.opensuse.org/tests/1509083#step/NM_wpa2_enterprise/37 reproduced. call trace found in NM_wpa2_enterprise-journal.log
see https://openqa.opensuse.org/tests/1509083/file/NM_wpa2_enterprise-journal.log

Dec 15 04:54:14.798109 susetest kernel: Call Trace:
Dec 15 04:54:14.798161 susetest kernel: [c0000000027478f0] [c000000002747950] 0xc000000002747950 (unreliable)
Dec 15 04:54:14.798199 susetest kernel: [c000000002747ad0] [c00000000002338c] __switch_to+0x2ac/0x490
Dec 15 04:54:14.798243 susetest kernel: [c000000002747b30] [c000000000d208d0] __schedule+0x2d0/0x960
Dec 15 04:54:14.798280 susetest kernel: [c000000002747c10] [c000000000d20fb0] schedule+0x50/0x100
Dec 15 04:54:14.798315 susetest kernel: [c000000002747c40] [c000000000d2739c] schedule_hrtimeout_range_clock+0x14c/0x180
Dec 15 04:54:14.798351 susetest kernel: [c000000002747cd0] [c0000000005025e4] ep_poll+0x2d4/0x4d0
Dec 15 04:54:14.798387 susetest kernel: [c000000002747d90] [c0000000005028e4] do_epoll_wait+0x104/0x130
Dec 15 04:54:14.798423 susetest kernel: [c000000002747de0] [c000000000504ca4] sys_epoll_pwait+0x94/0x130
Dec 15 04:54:14.798467 susetest kernel: [c000000002747e20] [c00000000000b288] system_call+0x5c/0x70
Dec 15 04:54:14.798504 susetest kernel: kthreadd S 0 2 0 0x00000808
Dec 15 04:54:14.798540 susetest kernel: Call Trace:
Dec 15 04:54:14.798575 susetest kernel: [c000000002743a30] [c000000002743aa0] 0xc000000002743aa0 (unreliable)
Dec 15 04:54:14.798620 susetest kernel: [c000000002743c10] [c00000000002338c] __switch_to+0x2ac/0x490
Dec 15 04:54:14.798665 susetest kernel: [c000000002743c70] [c000000000d208d0] __schedule+0x2d0/0x960
Dec 15 04:54:14.798701 susetest kernel: [c000000002743d50] [c000000000d20fb0] schedule+0x50/0x100
Dec 15 04:54:14.798737 susetest kernel: [c000000002743d80] [c00000000016d000] kthreadd+0x300/0x340
Dec 15 04:54:14.798781 susetest kernel: [c000000002743e20] [c00000000000b660] ret_from_kernel_thread+0x5c/0x7c
Dec 15 04:54:14.798817 susetest kernel: rcu_gp I 0 3 2 0x00000808
Dec 15 04:54:14.798853 susetest kernel: Call Trace:
Dec 15 04:54:14.798888 susetest kernel: [c00000000275f9b0] [c00000000275fa20] 0xc00000000275fa20 (unreliable)
Dec 15 04:54:14.798924 susetest kernel: [c00000000275fb90] [c00000000002338c] __switch_to+0x2ac/0x490
Dec 15 04:54:14.798968 susetest kernel: [c00000000275fbf0] [c000000000d208d0] __schedule+0x2d0/0x960
Dec 15 04:54:14.799004 susetest kernel: [c00000000275fcd0] [c000000000d20fb0] schedule+0x50/0x100
Dec 15 04:54:14.799040 susetest kernel: [c00000000275fd00] [c0000000001620d0] rescuer_thread+0x400/0x530
Dec 15 04:54:14.799075 susetest kernel: [c00000000275fdb0] [c00000000016c01c] kthread+0x1ac/0x1c0
Dec 15 04:54:14.799111 susetest kernel: [c00000000275fe20] [c00000000000b660] ret_from_kernel_thread+0x5c/0x7c
Dec 15 04:54:14.799147 susetest kernel: rcu_par_gp I 0 4 2 0x00000808
Dec 15 04:54:14.799182 susetest kernel: Call Trace:
Dec 15 04:54:14.799217 susetest kernel: [c00000000275b9b0] [c00000000275ba20] 0xc00000000275ba20 (unreliable)
Dec 15 04:54:14.799252 susetest kernel: [c00000000275bb90] [c00000000002338c] __switch_to+0x2ac/0x490
Dec 15 04:54:14.799288 susetest kernel: [c00000000275bbf0] [c000000000d208d0] __schedule+0x2d0/0x960
Dec 15 04:54:14.799324 susetest kernel: [c00000000275bcd0] [c000000000d20fb0] schedule+0x50/0x100
Dec 15 04:54:14.799359 susetest kernel: [c00000000275bd00] [c0000000001620d0] rescuer_thread+0x400/0x530
Dec 15 04:54:14.799394 susetest kernel: [c00000000275bdb0] [c00000000016c01c] kthread+0x1ac/0x1c0
Dec 15 04:54:14.799430 susetest kernel: [c00000000275be20] [c00000000000b660] ret_from_kernel_thread+0x5c/0x7c
Dec 15 04:54:14.799465 susetest kernel: kworker/0:0 I 0 5 2 0x00000808
Dec 15 04:54:14.799500 susetest kernel: Workqueue: 0x0 (events)
Dec 15 04:54:14.799536 susetest kernel: Call Trace:
Dec 15 04:54:14.799570 susetest kernel: [c00000000274b9c0] [c00000000274ba20] 0xc00000000274ba20 (unreliable)
Dec 15 04:54:14.799606 susetest kernel: [c00000000274bba0] [c00000000002338c] __switch_to+0x2ac/0x490
Dec 15 04:54:14.799641 susetest kernel: [c00000000274bc00] [c000000000d208d0] __schedule+0x2d0/0x960
Dec 15 04:54:14.799677 susetest kernel: [c00000000274bce0] [c000000000d20fb0] schedule+0x50/0x100
Dec 15 04:54:14.799712 susetest kernel: [c00000000274bd10] [c0000000001617a0] worker_thread+0x130/0x660
Dec 15 04:54:14.799748 susetest kernel: [c00000000274bdb0] [c00000000016c01c] kthread+0x1ac/0x1c0
Dec 15 04:54:14.799783 susetest kernel: [c00000000274be20] [c00000000000b660] ret_from_kernel_thread+0x5c/0x7c
Dec 15 04:54:14.799819 susetest kernel: kworker/0:0H I 0 6 2 0x00000808
Dec 15 04:54:14.799855 susetest kernel: Call Trace:
Dec 15 04:54:14.799890 susetest kernel: [c0000000027579c0] [c000000002757a30] 0xc000000002757a30 (unreliable)
Dec 15 04:54:14.799926 susetest kernel: [c000000002757ba0] [c00000000002338c] __switch_to+0x2ac/0x490
Dec 15 04:54:14.799971 susetest kernel: [c000000002757c00] [c000000000d208d0] __schedule+0x2d0/0x960
Dec 15 04:54:14.800007 susetest kernel: [c000000002757ce0] [c000000000d20fb0] schedule+0x50/0x100
Dec 15 04:54:14.800043 susetest kernel: [c000000002757d10] [c0000000001617a0] worker_thread+0x130/0x660
Dec 15 04:54:14.800078 susetest kernel: [c000000002757db0] [c00000000016c01c] kthread+0x1ac/0x1c0
Dec 15 04:54:14.800114 susetest kernel: [c000000002757e20] [c00000000000b660] ret_from_kernel_thread+0x5c/0x7c
Dec 15 04:54:14.800150 susetest kernel: mm_percpu_wq I 0 8 2 0x00000808

Actions
Copy link
 #28

Updated by zluo over 3 years ago

https://bugzilla.opensuse.org/show_bug.cgi?id=1180053 has been filed for call trace from kernel.

Actions
Copy link
 #29

Updated by zluo over 3 years ago

https://openqa.opensuse.org/tests/1510746#step/NM_wpa2_enterprise/36 shows with softfail, but since this is an issue about call trace from kernel, so this is not possible to workaround.
my test PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11622/

Actions
Copy link
 #30

Updated by okurz over 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1317724

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #31

Updated by zluo over 3 years ago

  • Status changed from In Progress to Blocked
Actions
Copy link
 #32

Updated by okurz about 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1317724

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #33

Updated by okurz about 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1317724

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #34

Updated by okurz about 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1317724

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #35

Updated by okurz about 3 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: extra_tests_on_gnome
https://openqa.opensuse.org/tests/1317724

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #36

Updated by zluo about 2 years ago

  • Status changed from Blocked to Resolved

NM_wpa2_enterprise doesn't have any issue for a quite long time. I checked this for ppc64:
https://openqa.opensuse.org/tests/2240865

so this has been resolved.

Actions
Copy link

Also available in: Atom PDF