action #164676
closed[alert][o3] test fails in setup_multimachine to reach other machines/instances from w20 size:S
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-ping_client@64bit fails in
setup_multimachine
with
Test died: ping with packet size 100 failed, problems with MTU size are expected. If it is multi-machine job, it can be GRE tunnel setup issue. at opensuse/lib/utils.pm line 1978.
Test suite description¶
Multimachine Ping client test. Maintainer: dheidler@suse.de
Reproducible¶
Fails since (at least) Build 2024-07-30T02:51+00:00 (current job)
Expected result¶
Last good: 20240729 (or more recent)
Suggestions¶
- Confirm if the issue is reproducible e.g. by running 100 jobs on worker20, running 100 jobs on different workers, checking if there is any other jobs failing in a similar way
- Check whether the MM setup on o3 is still valid
- Consider using the
PARALLEL_ONE_HOST_ONLY=1
setting on o3 (as we already do on OSD)
Further details¶
Always latest result in this scenario: latest
Updated by livdywan 5 months ago
- Status changed from New to In Progress
- Assignee set to livdywan
Looking at Next & previous results I see no other occurrences 🤔
Updated by livdywan 5 months ago · Edited
livdywan wrote in #note-1:
Looking at Next & previous results I see no other occurrences 🤔
openqa-clone-job --skip-download --skip-chained-deps --repeat=100 --within-instance https://openqa.opensuse.org 4365956 WORKER_CLASS=openqaworker20 _GROUP=0 BUILD+=poo#4365956
Updated by openqa_review 5 months ago
- Due date set to 2024-08-14
Setting due date based on mean cycle time of SUSE QE Tools
Updated by okurz 5 months ago
Related what should help: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19557
Updated by okurz 5 months ago
- Due date deleted (
2024-08-14) - Status changed from In Progress to Resolved
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19557 merged. We will see the effect of that in the tests that we maintain and will be notified so we don't need to wait for further confirmation in this ticket. The original issue seems to be a one-off which is not reproducible so no further action planned besides the mentioned improvement.