Project

General

Profile

Actions
Copy link

action #119494

open

[y][sporadic] test fails in yast2_nfs_server in 5 out of 25 cases to ping

Added by okurz over 1 year ago. Updated about 1 month ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-10-27
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-textmode@ppc64le fails in
yast2_nfs_server

Reproducible

yes, but sporadic.
In https://openqa.opensuse.org/tests/2512467#next_previous we see 5/25 failures so 20% of the cases.

Expected result

Last good: 20221025 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by okurz over 1 year ago

  • Subject changed from [sporadic] test fails in yast2_nfs_server in 5 out of 25 cases to ping to [y][sporadic] test fails in yast2_nfs_server in 5 out of 25 cases to ping
Actions
Copy link
 #2

Updated by okurz over 1 year ago

  • Priority changed from Normal to High
Actions
Copy link
 #3

Updated by openqa_review over 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: textmode
https://openqa.opensuse.org/tests/2868161#step/yast2_nfs_server/1

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

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #4

Updated by slo-gin over 1 year ago

This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link
 #5

Updated by slo-gin over 1 year ago

This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link
 #6

Updated by slo-gin about 1 year ago

This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link
 #7

Updated by slo-gin about 1 month ago

This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link

Also available in: Atom PDF