action #138302
closedEnsure automated openQA tests verify that os-autoinst-setup-multi-machine sets up valid networking size:M
Description
Motivation¶
Thanks to #133025 we cover os-autoinst-setup-multi-machine in openQA tests. However currently those tests never verify the setup and would at best catch more trivial issues with running the script.
Acceptance criteria¶
- AC1: Broken networking prepared by os-autoinst-setup-multi-machine is visible as a failed openQA test job
Suggestions¶
- The os-autoinst-setup-multi-machine script is already executed in this test: https://openqa.opensuse.org/tests/3658269 but it is not verified that the network actually works
- We even already start a test there (but not check the result): https://openqa.opensuse.org/tests/3658269#step/start_test/5
- See https://openqa.opensuse.org/tests/3766545 (openqa_bootstrap test) where we check both the API and the webui for a nested openQA test
- Create a very simple scenario where one node pings the other (maybe even with dhcp before)
Updated by livdywan 6 months ago
- Copied from action #133025: Configure Virtual Interfaces instructions do not work on Leap 15.5 size:M added
Updated by dheidler 6 months ago
Followup on #133025
As of now the openQA-in-openQA test calls the os-autoinst-setup-multi-machine script,
but only checks that it runs through without failure.
Still afterwards only a single test is executed.
The testsuite should be extended to run a real multi machine job to verify that the
setup created by the script works.
Updated by dheidler 5 months ago
- Subject changed from Ensure automated openQA tests verify that os-autoinst-setup-multi-machine sets up valid networking to Ensure automated openQA tests verify that os-autoinst-setup-multi-machine sets up valid networking size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by openqa_review 5 months ago
- Due date set to 2023-12-16
Setting due date based on mean cycle time of SUSE QE Tools
Updated by openqa_review 4 months ago
- Due date set to 2024-01-04
Setting due date based on mean cycle time of SUSE QE Tools
Updated by livdywan 4 months ago
- Related to action #152098: [research][timeboxed:10h] Learn more about openvswitch with experimenting together size:S added
Updated by okurz 4 months ago
- Due date changed from 2024-01-04 to 2024-01-11
As discussed today:
So my full suggestion: Ensure that "full_run" from https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/tests/osautoinst/start_test.pm#L33 is actually executed as part of openQA-in-openQA tests, extend that test code to clone the "wireguard_client/server" scenario and just see what happens
Updated by dheidler 4 months ago
The wireguard testsuite can't be used because it needs internet access to install wireguard packages.
Internet access from the inner SUTs is not possible due to conflicting IP addresses.
So creating a simple ping testsuite that doesn't need to install any packages.
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18440
Updated by dheidler 3 months ago
- Blocked by action #153616: Prevent `duplicate key value violates unique constraint` on image uploads size:S added
Updated by dheidler 3 months ago
- Related to action #153766: [core][sporadic] Handle wild agetty better in tests/network/setup_multimachine.pm added
Updated by okurz 2 months ago
- Related to action #155170: [openqa-in-openqa] [sporadic] test fails in test_running: parallel_failed size:M added
Updated by okurz 2 months ago
- Related to action #155173: [openqa-in-openqa] [sporadic] test fails in openqa_worker: os-autoinst-setup-multi-machine timed out size:M added