action #176076
Updated by okurz 3 months ago
## Observation
openQA test in scenario sle-15-SP6-BCI-Updates-s390x-golang_stable_on_SLES_15-SP4_podman@s390x-kvm run into MAX_JOB_TIME exceeded in
[bootloader_zkvm](https://openqa.suse.de/tests/16551116/modules/bootloader_zkvm/steps/5)
This was brought up in Slack #eng-testing by @MDoucha in https://suse.slack.com/archives/C02CANHLANP/p1737624344362149
## Reproducible
Seems to fail consistently looking at worker history like
https://openqa.suse.de/admin/workers/2660
## Expected result
Last good: https://openqa.suse.de/tests/16506528 from 2025-01-20 09:14:53Z
## Acceptance criteria
* **AC1:** Clear error output well before MAX_JOB_TIME about the actual cause
* **AC2:** Consistently stable tests again on s390x-kvm within the OSD infrastructure
## Suggestions
* Try to reproduce manually or using developer mode
* Trigger investigation jobs with openqa-investigate to bisect between impact of product, tests, infrastructure
* Gather statistics, e.g. using `openqa-clone-job --repeat`
* Ensure that the error output is clear and helps to distinguish between test issues and infrastructure issues
* Fix the actual underlying problem
## Further details
Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=BCI-Updates&machine=s390x-kvm&test=golang_stable_on_SLES_15-SP4_podman&version=15-SP6)
While this is a test on OSD so far it looks like a generic openQA s390x problem so not assigning with tag "infra"
Back