Project

General

Profile

action #40049

[functional][y] test fails in yast2_network_setup - need better logging w/o network to create product issue

Added by dimstar about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 19
Start date:
2018-08-21
Due date:
2018-09-25
% Done:

0%

Estimated time:
1.00 h
Difficulty:
medium

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_on_gnome@64bit fails in
yast2_network_setup

Reproducible

Fails since (at least) Build 20180813

Expected result

Last good: 20180812 (or more recent)

Acceptance criteria

  • AC1: The test module "yast2_network_setup" can provide logging information even if the network is down
  • AC2: The approach is reusable, e.g. usable by other test modules
  • AC3: Do not execute unnecessary extra steps in the generic post_fail_hook (to prevent failing jobs taking even longer without adding needed information)

Suggestions

  • As we do not have network when we broke the network either we can repair it before trying to upload logs as e.g. asmorodskyi did in wicked tests or we simply dump more to the serial port. Good candidates should be output from journalctl -u wicked and journalctl -u NetworkManager or just the whole journalctl or what the wicked test modules already do. In the post_fail_hook just add journalctl | tee /dev/$serialdev.
  • Find a proper base class for all "network related tests" and put the logic there

Further details

Always latest result in this scenario: latest

The test has network running at first, then switches to NetworkManager, which, according to the screenshots in the test, also comes up fine with network. Later on, the test resets back to wicked - at which point the network no longer comes up.

From a QA side of things we need to collect more information about this issue - and then we will most likely find a bug in the product (my first guess woulod be kernel 4.18)

as this seems only to happen after switching around with the network mode, I use this ticket for now to be able to tag the test (and ignore it)


Related issues

Related to openQA Tests - action #41429: [functional][y] test fails in yast2_network_setup - another case related to NM is the default network managementResolved2018-09-212018-10-09

History

#1 Updated by okurz about 4 years ago

  • Subject changed from test fails in yast2_network_setup to [functional][y] test fails in yast2_network_setup
  • Due date set to 2018-09-11
  • Priority changed from Normal to High
  • Target version set to Milestone 19

#2 Updated by okurz about 4 years ago

  • Subject changed from [functional][y] test fails in yast2_network_setup to [functional][y] test fails in yast2_network_setup - need better logging w/o network to create product issue
  • Description updated (diff)
  • Estimated time set to 5.00 h
  • Difficulty set to medium

#3 Updated by okurz about 4 years ago

  • Status changed from New to Workable

#4 Updated by riafarov about 4 years ago

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

#5 Updated by riafarov about 4 years ago

  • Status changed from In Progress to Feedback

#6 Updated by riafarov about 4 years ago

  • Status changed from Feedback to Resolved

PR merged, no animal wicked test was hurt on osd.

#7 Updated by riafarov about 4 years ago

  • Status changed from Resolved to In Progress

#8 Updated by riafarov about 4 years ago

  • Status changed from In Progress to Feedback

#9 Updated by riafarov about 4 years ago

  • Due date changed from 2018-09-11 to 2018-09-25

PR is still open

#10 Updated by riafarov about 4 years ago

  • Estimated time changed from 5.00 h to 1.00 h

#11 Updated by riafarov about 4 years ago

  • Status changed from Feedback to Resolved

PR merged, it's a fallback, so no run on o3/osd will trigger introduced code.

#12 Updated by okurz about 4 years ago

  • Related to action #41429: [functional][y] test fails in yast2_network_setup - another case related to NM is the default network management added

Also available in: Atom PDF