Project

General

Profile

Actions
Copy link

action #64625

closed

[sporadic] test fails in NM_wpa2_enterprise - Fail to connect

Added by ggardet_arm about 4 years ago. Updated over 3 years ago.

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

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-15.2-DVD-aarch64-extra_tests_on_gnome@aarch64 fails in
NM_wpa2_enterprise

It fail to connect to wifi. It seems that the password length does not match. See: https://openqa.opensuse.org/tests/1208161#step/NM_wpa2_enterprise/10
Maybe add an assert_screen to check password length?

Test suite description

Maintainer: asmorodskyi, okurz. Extra tests which were designed to run on gnome

Reproducible

Fails since (at least) Build 130.1

Expected result

Last good: 129.1 (or more recent)

Further details

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Is duplicate of openQA Tests - action #64042: [qe-core][functional][sporadic] test fails in NM_wpa2_enterprise: "dhcp4 (wlan1): request timed out" Leap15.2 ppc64leResolvedzluo2020-03-02

Actions
Actions
Copy link
 #1

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/1220461

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
 #2

Updated by ggardet_arm about 4 years ago

  • Subject changed from test fails in NM_wpa2_enterprise - Fail to connect to [sporadic] test fails in NM_wpa2_enterprise - Fail to connect
Actions
Copy link
 #3

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/1246878

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 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/1278367

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 ggardet_arm almost 4 years ago

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

Vs 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-
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/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
 #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/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
 #9

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
 #10

Updated by SLindoMansilla over 3 years ago

  • Is duplicate of action #64042: [qe-core][functional][sporadic] test fails in NM_wpa2_enterprise: "dhcp4 (wlan1): request timed out" Leap15.2 ppc64le added
Actions
Copy link
 #11

Updated by SLindoMansilla over 3 years ago

  • Status changed from New to Rejected
  • Assignee set to SLindoMansilla
  • Target version set to Milestone 30

Duplicate of #64042

Actions
Copy link
 #12

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
 #13

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
 #14

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
 #15

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

Also available in: Atom PDF