Project

General

Profile

Actions
Copy link

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 8 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Feature requests
Target version:
openQA Project - Ready
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 open — 1 closed)

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

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

Actions
Actions
Copy link
 #1

Updated by livdywan about 1 year ago

  • Copied from action #135407: [tools] Measure to mitigate websockets overload by workers and revert it size:M added
Actions
Copy link
 #2

Updated by okurz about 1 year ago

  • Project changed from openQA Project to openQA Infrastructure
  • Description updated (diff)
  • Status changed from New to Blocked
  • Assignee set to okurz
  • Target version set to Tools - Next

Replaced "worker32" in AC with "worker31"

First waiting for #136013

Actions
Copy link
 #3

Updated by livdywan about 1 year ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by okurz about 1 year ago

  • Copied to action #138707: Re-enable worker32 for multi-machine tests in production added
Actions
Copy link
 #5

Updated by okurz about 1 year ago

  • Target version changed from Tools - Next to future
Actions
Copy link
 #6

Updated by openqa_review about 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: ovs-server
https://openqa.opensuse.org/tests/3749903#step/ovs_server/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #7

Updated by openqa_review 8 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: ovs-client
https://openqa.suse.de/tests/13793290#step/ovs_client/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 100 days if nothing changes in this ticket.

Actions
Copy link
 #8

Updated by livdywan 8 months ago ยท Edited

  • Status changed from Blocked to New

With #136013 having been resolved I guess this isn't blocked and could be estimated once it ends up on the backlog

Actions
Copy link
 #9

Updated by okurz 8 months ago

  • Category set to Feature requests
  • Status changed from New to Resolved
  • Target version changed from future to Ready

worker31 is already enabled for multi-machine testing. https://openqa.suse.de/admin/workers/2577 shows that the worker has "tap". https://openqa.suse.de/tests/13808976 is just one of many jobs to show that working. https://openqa.suse.de/tests/13793290 was not even on worker31 but worker37. https://openqa.suse.de/tests/13687822 is an example of a successful run on worker37, 14 days ago so there is no clearly reproducible problem at least. I removed the comment from https://openqa.suse.de/tests/13793290#comments as I assume that the problem is a different one.

Actions
Copy link

Also available in: Atom PDF