action #117340
closedopenQA-in-openQA test openqa_install+publish fails in start_test size:M
Description
Observation¶
openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in
start_test
Test suite description¶
Maintainer: okurz@suse.de Test for installation of openQA itself. To be used with "openqa" distri. Publishes an qcow2 image including the openQA installation ready to run as an appliance.
Reproducible¶
Fails since (at least) Build :TW.12329
Expected result¶
Last good: :TW.12328 (or more recent)
Further details¶
Always latest result in this scenario: latest
Suggestions¶
- It stopped failing recently - it seems to be flakey
- Investigate https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/tests/osautoinst/start_test.pm
- Save the result in a variable to facilitate debugging
- Look into the OPENQA_CLI_RETRIES (it's supposed to retry 5 times and sleep 3s), but autoinst-log timestamps look a bit different
Updated by tinita over 1 year ago
- Project changed from openQA Tests to openQA Project
- Category deleted (
Bugs in existing tests)
Updated by livdywan over 1 year ago
- Subject changed from openQA-in-openQA test openqa_install+publish fails in start_test to openQA-in-openQA test openqa_install+publish fails in start_test size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by mkittler over 1 year ago
- Status changed from Workable to In Progress
The use of OPENQA_CLI_RETRIES makes only a difference for 500 responses. So we should not be surprised that it doesn't help here.
Save the result in a variable to facilitate debugging
I'll create a PR.
Updated by mkittler over 1 year ago
PR for better output in the error case: https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/101
Updated by openqa_review over 1 year ago
- Due date set to 2022-10-22
Setting due date based on mean cycle time of SUSE QE Tools
Updated by mkittler over 1 year ago
- Status changed from In Progress to Feedback
The PR has been merged. I suppose now we just have to wait until the problem occurs again.
Updated by livdywan over 1 year ago
- Status changed from Feedback to Resolved
We don't know if this will or won't occur again, and we have a minimal improvement, hence resolving