action #121567
Updated by tinita over 1 year ago
## Observation
openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in
[test_running](https://openqa.opensuse.org/tests/2931073/modules/test_running/steps/1)
## 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.12917](https://openqa.opensuse.org/tests/2931073) (current job)
## Expected result
Last good: [:TW.12916](https://openqa.opensuse.org/tests/2931061) (or more recent)
## Further details
Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=openqa&flavor=dev&machine=64bit-2G&test=openqa_install%2Bpublish&version=Tumbleweed)
Looking at the video and in the log `retry` doesn't seem to do any retries:
```
[2022-12-06T12:02:51.501219+01:00] [debug] <<< testapi::assert_script_run(cmd="retry -s 30 -r 5 -- openqa-cli api jobs state=running state=done | ack --passthru --color \"running|done\"", fail_message="", timeout=300, quiet=undef)
...
[2022-12-06T12:02:58.353973+01:00] [info] ::: basetest::runtest: # Test died: command 'retry [...]
```
That's only 7 seconds.
I guess that's because the openqa-cli command passes, and the ack fails, but the retry is attached to the openqa-cli command.
Possibly related: https://github.com/os-autoinst/openQA/pull/4935 Avoid running jobs with undetermined worker address