action #54407
closed[sle][functional][y][timeboxed:8h] adjust yast2_lan_restart for s390x or remove from the schedule
0%
Description
checked the logs, timeout 180 seems to be too less, reboot could not made in time: wait_serial: yast2-lan-status-0: fail
We need to investigate if that's a bug. If it's a bug we should check if there is workaround or not.
If test needs adjustments, please, file separate ticket with details what has to be adjusted and temporally remove it from the schedule for s390x.
Observation¶
openQA test in scenario sle-12-SP5-Server-DVD-s390x-extra_tests_on_gnome@s390x-kvm-sle12 fails in
yast2_lan_restart
Test suite description¶
Maintainer: asmorodskyi, okurz. Extra tests which were designed to run on gnome
Reproducible¶
Fails since (at least) Build 0114
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by riafarov almost 5 years ago
- Subject changed from [sle][functional]test fails in yast2_lan_restart - timeout issue for reboot to [sle][functional][y] test fails in yast2_lan_restart - timeout issue for reboot
- Priority changed from High to Normal
- Target version set to Milestone 26
Test never worked on s390x, so same story as in #54239
Updated by riafarov over 4 years ago
- Subject changed from [sle][functional][y] test fails in yast2_lan_restart - timeout issue for reboot to [sle][functional][y] adjust yast2_lan_restart for s390x or remove from the schedule
- Due date set to 2019-08-13
- Target version changed from Milestone 26 to Milestone 27
Updated by JERiveraMoya over 4 years ago
- Due date changed from 2019-08-13 to 2019-08-27
Updated by riafarov over 4 years ago
- Subject changed from [sle][functional][y] adjust yast2_lan_restart for s390x or remove from the schedule to [sle][functional][y][timeboxed:8h] adjust yast2_lan_restart for s390x or remove from the schedule
- Description updated (diff)
- Status changed from New to Workable
Updated by riafarov over 4 years ago
- Status changed from Workable to Feedback
Problem is that https://openqa.suse.de/tests/3242592#step/yast2_lan_restart_devices/66 on this step we don't edit eth0, as page is not loaded, but blindly press keys not changing the configuration. I've created proper needle, retriggering the job,
Updated by riafarov over 4 years ago
So in the end it's a bug, https://bugzilla.suse.com/show_bug.cgi?id=1145943 I've created PR to exclude testing of bond devices on zKVM. Checking if VLAN will fail or not.