action #136346
open[qe-sap] test fails in check_after_reboot auto_review:"Test died: Cluster/resources did not start within 240 seconds":retry
0%
Description
Observation¶
openQA test in scenario sle-12-SP5-Server-DVD-HA-Incidents-x86_64-qam_ha_hawk_haproxy_node01@64bit fails in
check_after_reboot
with "Test died: Cluster/resources did not start within 240 seconds".
observed in some jobs.
Reproducible¶
Fails since (at least) Build :30669:nethogs (current job)
https://openqa.suse.de/tests/12192446#comment-1028373 shows that this is a sporadic test issue.
Find jobs referencing this ticket with the help of
https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label ,
call openqa-query-for-job-label poo#136346
Expected result¶
Last good: :30641:python3 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by openqa_review 6 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: qam_ha_hawk_haproxy_node02
https://openqa.suse.de/tests/13168978#step/check_after_reboot/1
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 28 days if nothing changes in this ticket.
Updated by tinita 4 months 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.
Updated by slo-gin about 2 months ago
- Priority changed from High to Normal
The ticket will be set to the next lower priority Normal