action #55127
open
[qe-core][functional][u] test fails in shutdown
0%
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
Updated by StefanBruens about 4 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
Updated by SLindoMansilla about 4 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
Updated by StefanBruens about 4 years ago
- Status changed from New to In Progress
- Assignee set to StefanBruens
Updated by okurz about 4 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
Updated by okurz almost 4 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
Updated by okurz almost 4 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 4 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 4 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 4 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz almost 4 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by SLindoMansilla almost 4 years ago
- Status changed from In Progress to Resolved
Verified on O3: https://openqa.opensuse.org/tests/1114988#next_previous
Updated by okurz 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: kubeadm
https://openqa.opensuse.org/tests/1132023
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by okurz 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: kubeadm@64bit-2G
https://openqa.opensuse.org/tests/1146635
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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: kubeadm@64bit-2G-HD40G
https://openqa.opensuse.org/tests/2270360
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
Updated by okurz over 1 year 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.
Updated by