action #115334
closed[tools][openqa-in-openqa] test fails in start_test - likely due to o3 temporarily not available
Description
Observation¶
openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in
start_test
with "503 Service Unavailable". Likely we should retry on such cases, maybe at best already within openqa-clone-job?
Reproducible¶
Seems to have failed only this once. The former and later job in the scenario https://openqa.opensuse.org/tests/2516550#next_previous as well as the investigation retry all passed.
Expected result¶
Last good: :TW.12048 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz over 2 years ago
- Project changed from openQA Tests (public) to openQA Project (public)
- Category changed from Bugs in existing tests to Feature requests
Updated by okurz over 2 years ago
- Status changed from New to In Progress
First use openqa-cli replacing openqa-client uses: https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/97
Updated by okurz over 2 years ago
- Status changed from In Progress to Feedback
Updated by okurz over 2 years ago
Both PRs merged. Retriggered tests on https://openqa.opensuse.org/tests/overview?groupid=24&build=%3ATW.12060&version=Tumbleweed&distri=openqa
Updated by okurz over 2 years ago
- Status changed from Feedback to Resolved
All three green. We don't know if that would cover temporary outages of o3 but I don't want to kill o3 just to test that ;)