action #106996
closedcoordination #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
Description
Updated by okurz about 2 years ago
- Copied from action #106867: os-autoinst: local svirt testing instructions size:M added
Updated by okurz about 2 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
Updated by livdywan about 2 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
Updated by mkittler about 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
Updated by mkittler about 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.