Project

General

Profile

Actions

action #138707

open

Re-enable worker32 for multi-machine tests in production

Added by okurz 8 months ago. Updated 8 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2023-10-28
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: Worker32 is known to successfully execute multi-machine jobs

Suggestions


Related issues 3 (1 open2 closed)

Related to openQA Project - action #138698: significant increase in multi-machine test failures on OSD since 2023-10-25, e.g. test fails in support_server/setup size:MResolvedmkittler2023-10-27

Actions
Copied from openQA Infrastructure - action #137756: Re-enable worker31 for multi-machine tests in production auto_review:"tcpdump.+check.log.+timed out at"Resolvedokurz

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

Actions
Actions #1

Updated by okurz 8 months ago

  • Copied from action #137756: Re-enable worker31 for multi-machine tests in production auto_review:"tcpdump.+check.log.+timed out at" added
Actions #2

Updated by okurz 8 months ago

  • Related to action #138698: significant increase in multi-machine test failures on OSD since 2023-10-25, e.g. test fails in support_server/setup size:M added
Actions #3

Updated by okurz 8 months ago

  • Description updated (diff)
Actions #4

Updated by okurz 8 months ago

  • Description updated (diff)
Actions #5

Updated by okurz 8 months ago

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

Updated by livdywan 8 months ago

  • Description updated (diff)
Actions #7

Updated by livdywan 8 months ago

  • Copied to action #139070: Re-enable worker34 for multi-machine tests in production added
Actions

Also available in: Atom PDF