Project

General

Profile

Actions
Copy link

action #95806

closed

test fails in yast2_lan_device_settings to select dynamic DHCP and hostname field

Added by okurz over 3 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
Current
Start date:
2021-07-21
Due date:
% Done:

0%

Estimated time:

Description

Observation

openQA test in scenario sle-12-SP4-Server-DVD-Updates-x86_64-mau-extratests-yast2ui-textmode@64bit fails in
yast2_lan_device_settings
as the test tries to select the hostname field but dynamic DHCP address assignment could not be selected.

This already failed in before, e.g. in https://openqa.suse.de/tests/6319847#step/yast2_lan_device_settings/56 one month ago

Test suite description

Run console tests against aggregated test repo

Reproducible

Fails since (at least) Build 20210721-2 (current job)

Expected result

Last good: 20210721-1 (or more recent)

Suggestions

  • Stabilize test
  • Please provide a maintainer email address in the test suite description

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by okurz over 3 years ago

  • Subject changed from [y][yast][qam][qe-update-validation][sporadic] test fails in yast2_lan_device_settings to select "dynamic" DHCP and hostname field to [y][yast][qam][qe-update-validation][sporadic] test fails in yast2_lan_device_settings to select dynamic DHCP and hostname field auto_review:"match=hostname-localhost-removed timed out after 1":retry
Actions
Copy link
 #2

Updated by openqa_review 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: mau-extratests-yast2ui-textmode
https://openqa.suse.de/tests/6663790

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" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed
Actions
Copy link
 #3

Updated by oorlov over 3 years ago

  • Tags set to qe-yast-refinement
  • Project changed from openQA Tests (public) to qe-yam
  • Subject changed from [y][yast][qam][qe-update-validation][sporadic] test fails in yast2_lan_device_settings to select dynamic DHCP and hostname field auto_review:"match=hostname-localhost-removed timed out after 1":retry to test fails in yast2_lan_device_settings to select dynamic DHCP and hostname field
  • Category deleted (Bugs in existing tests)
  • Priority changed from Urgent to Normal
  • Target version set to Current

Lowering the priority as this is not failing permanently. It is sporadic fail and requires some time for investigations.

Also, this test module should be considered to be removed for this test suite as it uses legacy code that we do not use in YaST job Group anymore.

We should also consider if new test modules 'yast2_lan_restart_bridge', 'yast2_lan_restart_vlan', 'yast2_lan_restart_bond' can be simply adapted for this test suite.

Actions
Copy link
 #4

Updated by openqa_review 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: mau-extratests-yast2ui-textmode
https://openqa.suse.de/tests/7075844

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" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions
Copy link
 #5

Updated by oorlov over 3 years ago

  • Tags deleted (qe-yast-refinement)

Removed from refinement for now, as it didn't fail for a while. So, we'll come back to it later when more statistics will be gathered.

Actions
Copy link
 #6

Updated by okurz over 3 years ago

oorlov wrote:

Lowering the priority as this is not failing permanently. It is sporadic fail and requires some time for investigations.

Please consider the impact on reviewers: Sporadic issues are worse than consistently reproducing issues as label carry over will very likely not be able to carry over a bugref, hence my initial priority suggestion of "Urgent"

Also, this test module should be considered to be removed for this test suite as it uses legacy code that we do not use in YaST job Group anymore.

Removing the module could certainly be an easy remedy … if you want to simply accept the test coverage drop :)

Actions
Copy link
 #7

Updated by JERiveraMoya over 2 years ago

  • Status changed from New to Rejected

This test is not running for a long time, probably for the sake of stability in maintenance.
In future we will try to match better coverage between product validation and maintenance.

Actions
Copy link

Also available in: Atom PDF