QA » openQA Project » openQA Tests

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)