Project

General

Profile

action #55127

[qe-core][functional][u] test fails in shutdown

Added by StefanBruens about 3 years ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2019-08-05
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario microos-Staging:D-Staging-Kubic-DVD-x86_64-kubeadm@64bit-2G-HD40G fails in
shutdown

The test fails sometimes, but not always, the timeout seems to be slightly to low.

Test suite description

Reproducible

Fails since (at least) Build 202.5 (current job)

Expected result

Last good: 202.4 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by StefanBruens about 3 years ago

Did three reruns of failing tests, 2 of 3 succeeded on the 2nd attempt:

GOOD: https://openqa.opensuse.org/tests/999080
BAD: https://openqa.opensuse.org/tests/999081
GOOD: https://openqa.opensuse.org/tests/999082

#2 Updated by SLindoMansilla about 3 years ago

  • Subject changed from test fails in shutdown to [functional][u] test fails in shutdown
  • Priority changed from Normal to High

To be checked for duplicates

#3 Updated by StefanBruens almost 3 years ago

  • Status changed from New to In Progress
  • Assignee set to StefanBruens

#4 Updated by okurz almost 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: kubeadm@64bit-2G-HD40G
https://openqa.opensuse.org/tests/1030896

#5 Updated by okurz almost 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: kubeadm@64bit-2G-HD40G
https://openqa.opensuse.org/tests/1044156

#6 Updated by okurz almost 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: kubeadm@64bit-2G-HD40G
https://openqa.opensuse.org/tests/1056713

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

#7 Updated by okurz almost 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: kubeadm@64bit-2G-HD40G
https://openqa.opensuse.org/tests/1071663

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

#8 Updated by okurz almost 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: kubeadm@64bit-2G-HD40G
https://openqa.opensuse.org/tests/1086138

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

#9 Updated by okurz over 2 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: kubeadm@64bit-2G-HD40G
https://openqa.opensuse.org/tests/1099766

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

#10 Updated by okurz over 2 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: kubeadm@64bit-2G-HD40G
https://openqa.opensuse.org/tests/1112472

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

#11 Updated by SLindoMansilla over 2 years ago

  • Status changed from In Progress to Resolved

#12 Updated by okurz over 2 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: kubeadm
https://openqa.opensuse.org/tests/1132023

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

#13 Updated by okurz over 2 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: kubeadm@64bit-2G
https://openqa.opensuse.org/tests/1146635

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

#14 Updated by openqa_review 5 months ago

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

This bug is still referenced in a failing openQA test: kubeadm@64bit-2G-HD40G
https://openqa.opensuse.org/tests/2270360

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 56 days if nothing changes in this ticket.

#15 Updated by okurz 5 months ago

  • Subject changed from [functional][u] test fails in shutdown to [qe-core][functional][u] test fails in shutdown
  • Status changed from Resolved to New
  • Assignee deleted (StefanBruens)

reopening as reproduced in tests. @qe-core I suggest to remove the soft-fail reference to this progress ticket. Either make it a record_info with "ok" result to just reference the ticket and close the ticket again, or just accept longer shutdown times without ticket reference to actually reference a product issue with soft-fail. IMHO soft-fail references should not be used with progress tickets about test issues at all.

#16 Updated by szarate about 1 month ago

These tickets are not on high prio

#17 Updated by szarate about 1 month ago

  • Tags set to bulkupdate

These tickets are not on high pro

#18 Updated by szarate about 1 month ago

  • Priority changed from High to Normal

Also available in: Atom PDF