Project

General

Profile

Actions
Copy link

action #106996

closed

coordination #109668: [saga][epic] Stable and updated non-qemu backends for SLE validation

coordination #109656: [epic] Stable non-qemu backends

coordination #105699: [epic] 5 whys follow-up to s390x svirt jobs incomplete with unable to extract assets:.*/var/lib/libvirt/images/a.img" size:S

os-autoinst: describe how to take out a production worker instance for testing backend changes size:M

Added by okurz almost 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
mkittler
Category:
Organisational
Target version:
Ready
Start date:
2022-02-14
Due date:
% Done:

0%

Estimated time:

Description

Motivation

#105699#note-9

Acceptance criteria

  • AC1: instructions exist within our wiki how to take out a production worker instance for testing backend changes

Related issues 2 (0 open — 2 closed)

Copied from openQA Project (public) - action #106867: os-autoinst: local svirt testing instructions size:MResolvedmkittler2022-02-14

Actions
Copied to openQA Project (public) - action #106999: os-autoinst: Document the use of custom openQA backend commands to test os-autoinst changes on production workers size:MResolvedokurz2022-02-14

Actions
Actions
Copy link
 #1

Updated by okurz almost 3 years ago

  • Copied from action #106867: os-autoinst: local svirt testing instructions size:M added
Actions
Copy link
 #2

Updated by okurz almost 3 years ago

  • Copied to action #106999: os-autoinst: Document the use of custom openQA backend commands to test os-autoinst changes on production workers size:M added
Actions
Copy link
 #3

Updated by okurz almost 3 years ago

  • Parent task set to #105699
Actions
Copy link
 #4

Updated by livdywan almost 3 years ago

  • Subject changed from os-autoinst: describe how to take out a production worker instance for testing backend changes to os-autoinst: describe how to take out a production worker instance for testing backend changes size:M
  • Status changed from New to Workable
Actions
Copy link
 #5

Updated by mkittler over 2 years ago

  • Assignee set to mkittler
Actions
Copy link
 #6

Updated by mkittler over 2 years ago

  • Status changed from Workable to Feedback

Considering this is about svirt I've added a section in our Wiki explaining how to use a production svirt host (and also temporarily taking out the corresponding production worker instance) locally: https://progress.opensuse.org/projects/openqav3/wiki/Wiki#Use-production-svirt-host-for-testing-backend-changes-locally

Actions
Copy link
 #7

Updated by mkittler over 2 years ago

  • Status changed from Feedback to Resolved

I also mentioned the systemd commands in the existing section https://progress.opensuse.org/projects/openqav3/wiki/Wiki#Take-machines-out-of-salt-controlled-production. This should be good enough.

Actions
Copy link

Also available in: Atom PDF