action #155851
open
Establish dedicated k3s test machine
Added by ph03nix 4 months ago.
Updated 17 days ago.
Description
Since k3s is not available on s390x anymore (see #154996) we need a different approach for test runs that rely on k3s as kubernetes platform. We agreed that a possible approach is to create a dedicated k3s test machine in the O3 network, which can be used for openQA test runs.
This ticket is about setting up a dedicated k3s machine and adapt our test runs to use that machine, instead of a local k3s installation.
Please note, that for publiccloud tests we likely still need to rely on a local k3s installation.
Acceptance criteria¶
- Ask infra team for a dedicated VM (Be reasonable with the requested resources) in the O3 network
- Ensure that this machine can be accessed from OSD
- Adapt our test code to use this VM instead of installing k3s locally
- Document the new machine, either as a dedicated Confluence page in the Infrastructure Section or by a dedicated git repository in our qa-c gitlab group
- Related to action #152593: [refactoring] Move k3s part away from podman_pods added
- Description updated (diff)
This ticket was set to High priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
- Status changed from Workable to Blocked
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: kubectl_tests
https://openqa.suse.de/tests/14235616#step/kubectl/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- 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.
- Priority changed from High to Normal
This ticket was set to High priority but was not updated within the SLO period. The ticket will be set to the next lower priority Normal.
Also available in: Atom
PDF