action #162101
Updated by okurz 17 days ago
## Observation
All tests are failing on s390x because of timeouts. I tried it with a restart to identify the issue. I had to wait longer than 6 minutes for a start of the openQA job.
What is going wrong here? It seems, there can be a network problem between the mainframe and openQA.
openQA test in scenario opensuse-Tumbleweed-DVD-s390x-autoyast_zvm@s390x-zVM-vswitch-l2 fails in
[bootloader_start](https://openqa.opensuse.org/tests/4263651/modules/bootloader_start/steps/25)
## Test suite description
Create HDD for s390x textmode
## Reproducible
* Fails since (at least) Build [20240606](https://openqa.opensuse.org/tests/4255937)
* Clearly reproducible
## Expected result
Last good: [20240531](https://openqa.opensuse.org/tests/4243631) (or more recent)
The openQA tests are working also on s390x.
## Suggestions
* Compare to similar tests on osd
* Try out connection to s390x manually or use the developer mode to interactively debug
* Checkout previous results for s390x in https://openqa.opensuse.org/group_overview/34
* https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse&flavor=DVD&machine=s390x-zVM-vswitch-l2&test=autoyast_zvm&version=Tumbleweed fails the earliest, the other jobs in the same job group fail much later in a different module but seemingly also related to interaction with the network
* Parsing of console output might be broken due to network lag
## Further details
Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse&flavor=DVD&machine=s390x-zVM-vswitch-l2&test=autoyast_zvm&version=Tumbleweed)
Back