Project

General

Profile

Actions

action #135818

closed

[kernel] minimal reproducer for many multi-machine test failures in "ovs-client+ovs-server" test scenario when tests are run across different workers

Added by okurz about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2023-08-15
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:

Description

[tools] many multi-machine test failures in "ovs-client+ovs-server" test scenario when tests are run across different workers

Observation

See #134282-1

There is something wrong with multimachine network when tests are run across different workers. If is multimachine job forced to run on same worker, it is fine.

There are fails in core group: https://openqa.suse.de/tests/11843205#next_previous
Kernel group: https://openqa.suse.de/tests/11846943#next_previous
HPC: https://openqa.suse.de/tests/11845897#next_previous

The scenario is https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Server-DVD-Updates&machine=64bit&test=ovs-client&version=15-SP5

To be able to work more efficiently on #135773 it would be very helpful to have a minimum reproducer openQA test scenario.

Suggestions

  • Try to minimize the reproducer, e.g. skip test modules in openQA

Related issues 3 (0 open3 closed)

Related to openQA Tests (public) - action #136136: [qe-core] jobs scheduled for currently not available worker31 "ovs-server+client"Resolveddzedro2023-09-20

Actions
Has duplicate openQA Tests (public) - action #135200: [qe-core] Implement a ping check with custom MTU packet sizeRejecteddvenkatachala2023-08-15

Actions
Copied from openQA Infrastructure (public) - action #134282: [tools] network protocols failures on multimachine tests on HA/SAP size:S auto_review:"no candidate.*iscsi-target-overview-service-tab|yast2.+firewall.+services.+add.+zone":retryResolvednicksinger2023-08-15

Actions
Actions

Also available in: Atom PDF