Project

General

Profile

action #64042

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

Added by michel_mno 5 months ago. Updated 10 days ago.

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

0%

Estimated time:
42.00 h
Difficulty:
Duration:

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]: [1583047219.8364] device (wlan1): supplicant interface state: associated -> completed
Mar 01 02:20:19 susetest NetworkManager[3168]: [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]: [1583047219.8365] device (p2p-dev-wlan1): supplicant management interface state: associated -> completed
Mar 01 02:20:19 susetest NetworkManager[3168]: [1583047219.8714] device (wlan1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 01 02:20:19 susetest NetworkManager[3168]: [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]: [1583047265.5070] dhcp4 (wlan1): request timed out
Mar 01 02:21:05 susetest NetworkManager[3168]: [1583047265.5072] dhcp4 (wlan1): state changed unknown -> timeout
Mar 01 02:21:05 susetest NetworkManager[3168]: [1583047265.5074] dhcp4 (wlan1): canceled DHCP transaction
Mar 01 02:21:05 susetest NetworkManager[3168]: [1583047265.5074] dhcp4 (wlan1): state changed timeout -> done
Mar 01 02:21:05 susetest NetworkManager[3168]: [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]: [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)
===

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

History

#1 Updated by mgriessmeier 5 months 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

#2 Updated by okurz 5 months 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

#3 Updated by okurz 4 months 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

#4 Updated by okurz 4 months 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

#5 Updated by okurz 3 months 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

#6 Updated by okurz 3 months 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

#7 Updated by okurz 2 months 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

#8 Updated by okurz about 1 month 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

#9 Updated by SLindoMansilla 17 days 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

#10 Updated by SLindoMansilla 17 days ago

  • Description updated (diff)

#11 Updated by SLindoMansilla 10 days ago

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

Also available in: Atom PDF