Project

General

Profile

Actions

action #137756

closed

Re-enable worker31 for multi-machine tests in production auto_review:"tcpdump.+check.log.+timed out at"

Added by livdywan about 1 year ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Observation

See also #135407#note-34 for the original context. However that ticket doesn't provide so much of an explanation as it indicates what isn't the issue.

Acceptance criteria

  • AC1: Worker31 is known to successfully execute multi-machine jobs

Suggestions

  • Inspect failures in test jobs in so-far as they haven't been deleted yet
  • Try and find similarly failing cases elsewhere (so far unsuccessful)
  • Confirm what 10.0.2.101", "10.0.2.102" and "192.0.0.2 respectively are in the context of the test - maybe this could also be made clearer in the test?
  • Run the latest ovs-client test with something like PAUSE_AT=ovs_server and debug the SUT live e.g. openqa-clone-job --skip-chained-deps --parental-inheritance --within-instance https://openqa.suse.de 124375 14 TEST+=$i WORKER_CLASS=worker31 BUILD=poo137756 SKIP_MAINTENANCE_UPDATES=1 _GROUP=0

Related issues 2 (1 open1 closed)

Copied from openQA Project (public) - action #135407: [tools] Measure to mitigate websockets overload by workers and revert it size:MResolvedlivdywan2023-09-08

Actions
Copied to openQA Infrastructure (public) - action #138707: Re-enable worker32 for multi-machine tests in productionBlockedokurz2023-10-28

Actions
Actions

Also available in: Atom PDF