Project

General

Profile

Actions

action #115334

closed

[tools][openqa-in-openqa] test fails in start_test - likely due to o3 temporarily not available

Added by okurz about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-08-15
Due date:
% Done:

0%

Estimated time:

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

Actions #1

Updated by okurz about 2 years ago

  • Project changed from openQA Tests to openQA Project
  • Category changed from Bugs in existing tests to Feature requests
Actions #2

Updated by okurz about 2 years ago

  • Assignee set to okurz
Actions #3

Updated by okurz about 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

Actions #4

Updated by okurz about 2 years ago

  • Status changed from In Progress to Feedback
Actions #6

Updated by okurz about 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 ;)

Actions

Also available in: Atom PDF