action #123864

Updated by cdywan 4 months ago

## Observation

openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in
due to empty response from internal openQA instance

## Test suite description
Maintainer: 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.16820]( (current job) shows that this is a sporadic issue.

## Expected result

Last good: [:TW.16819]( (or more recent)

## Suggestions
* Catch the error if no jobs are found from an API query, maybe just `set -u` in bash is enough to fail when using variables?
* Right now the test module is looking for openQA assets to find the "most recent Tumbleweed build" and then query jobs but it can very well happen that assets are created and registered before all openQA jobs are scheduled so this approach can fail. Find a better way in to identify the latest job in a scenario and just clone that.
- If the above fails then consider adding a retry with waiting in between
- Ensure we're not waiting too long e.g. avoid waiting a day and spawning more jobs in-between
- The issue doesn't seem to be reproducible reliably

Further details

Always latest result in this scenario: [latest](