Project

General

Profile

Actions
Copy link

action #94765

closed

Bring openqaworker12 into production (w/o multi-machine test support) size:M

Added by okurz over 3 years ago. Updated 11 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
okurz
Category:
-
Target version:
QA (public, currently private due to #173521) - future
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:
infra

Description

Motivation

See #93050#note-15

Acceptance criteria

  • AC1: openqaworker12 is verified to be usable for production multi-machine tests
  • AC2: Same as AC1 but after additional reboots to ensure reboot stability
  • AC3: openqaworker12 is controlled over salt

Suggestions

  • Look into the error report of #93050#note-15
  • Find a good "single-machine test scenario" to verify
  • Bring the machine up with a dedicated worker class selection for investigation without tap, e.g. only openqaworker12
  • Fix any found problems
  • Accept salt key for openqaworker12 on osd sudo salt-key -y -a openqaworker12.suse.de
  • Apply full salt state and check for success
  • Unpause "openqaworker12: host up alert" https://stats.openqa-monitor.qa.suse.de/alerting/list?state=not_ok
  • Crosscheck monitoring results

Related issues 3 (0 open — 3 closed)

Copied from openQA Infrastructure (public) - action #93050: Proposal: Use openqaworker11 and openqaworker12 as normal workers and only pull out from production when necessaryResolvedokurz2021-05-24

Actions
Copied to openQA Infrastructure (public) - action #94783: Bring openqaworker11 into production including multi-machine test support (same as w12) size:MRejected2021-06-28

Actions
Copied to openQA Infrastructure (public) - action #95167: Bring openqaworker12 into production including multi-machine test supportRejectedokurz2021-07-07

Actions
Actions
Copy link

Also available in: Atom PDF