action #133025
closedConfigure Virtual Interfaces instructions do not work on Leap 15.5 size:M
Added by okurz 10 months ago. Updated 7 months ago.
Description
Motivation¶
http://open.qa/docs/#_configure_virtual_interfaces states ports on the firewall can be opened via firewall-cmd --new-service isotovideo but when I tried that on worker21 (new o3 prg2 worker), on Leap 15.5, that failed with an error message that this only works with --permanent. We should crosscheck all instructions and ensure they actually work as-is.
Acceptance criteria¶
- AC1: The same firewall commands that happen to be in the documentation are ensured to be working by automated tests
Suggestions¶
Provide a script that uses commands to open ports on a firewall, setup a test for it and refer to thatCheck that documented steps agree with what's being done byos-autoinst-setup-multi-machine- Use the documented commands in an openQA test and cross-reference so we somehow know if that stops working docs need to be updated
Further details¶
"ensured to be working" means it's either a separate script or it's ok to have the commands copied verbatim into something like openQA-in-openQA tests, no need for a document command scraper
Updated by livdywan 10 months ago
- Subject changed from http://open.qa/docs/#_configure_virtual_interfaces instructions do not work due to missing "permanent", at least on Leap 15.5 to http://open.qa/docs/#_configure_virtual_interfaces instructions do not work due to missing "permanent", at least on Leap 15.5 size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by openqa_review 10 months ago
- Due date set to 2023-08-09
Setting due date based on mean cycle time of SUSE QE Tools
Updated by okurz 10 months ago
- Related to action #115418: Setup ow19+20 to be able to run MM tests size:M added
Updated by okurz 10 months ago
- Status changed from In Progress to Feedback
- DONE https://github.com/os-autoinst/openQA/pull/5263 merged
- DONE But first cleanup in scenario definitions of os-autoinst-distri-openQA: https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/140 merged
- DONE Created https://github.com/os-autoinst/os-autoinst/pull/2347 for a multi-machine setup script
- DONE https://github.com/os-autoinst/openQA/pull/5269 openQA documentation updates
- DONE Cleanup https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/141
- Then maybe https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/138
Updated by okurz 10 months ago
- Related to action #132827: [tools][qe-core]test fails in rsync_client/salt-master, DNS resolve issue with workers "sapworker*" on multi-machine tests size:M added
Updated by okurz 9 months ago
- Related to action #132134: Setup new PRG2 multi-machine openQA worker for o3 size:M added
Updated by okurz 9 months ago
- Related to action #132137: Setup new PRG2 openQA worker for osd size:M added
Updated by livdywan 7 months ago
- Subject changed from http://open.qa/docs/#_configure_virtual_interfaces instructions do not work due to missing "permanent", at least on Leap 15.5 size:M to http://open.qa/docs/#_configure_virtual_interfaces instructions do not work on Leap 15.5 size:M
- Description updated (diff)
Updated by dheidler 7 months ago
- Status changed from Workable to In Progress
For reference: Setup for MM: https://progress.opensuse.org/issues/132134#note-38
Updated by openqa_review 7 months ago
- Due date set to 2023-10-31
Setting due date based on mean cycle time of SUSE QE Tools
Updated by okurz 7 months ago
https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/147 as an example how a quick and dirty test extension could look like. I don't even know if we package "os-autoinst-setup-multi-machine" right now
EDIT: We do, checked in a clean Tumbleweed container. /usr/bin/os-autoinst-setup-multi-machine so available from PATH.
Updated by okurz 7 months ago
As in the weekly unblocked we talked about the openQA-in-openQA tests using a gnome image with NetworkManager but we need to use wicked in both https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/.github/workflows/openqa.yml#L39 as well as https://github.com/os-autoinst/scripts/blob/master/_common#L242
The existing HDD image comes from the test suite "create_hdd_tumbleweed" in https://openqa.opensuse.org/admin/test_suites with settings
DESKTOP=gnome
HDDSIZEGB=40
INSTALLONLY=1
LINUXRC_KEXEC=3
NETBOOT=0
PUBLISH_HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-Tumbleweed@%MACHINE%.qcow2
PUBLISH_PFLASH_VARS=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-Tumbleweed@%MACHINE%-uefi-vars.qcow2
QEMU_COMPRESS_QCOW2=1
you already found "create_hdd_gnome_wicked" which has
BOOT_HDD_IMAGE=1
DESKTOP=gnome
HDDSIZEGB=20
HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%.qcow2
PUBLISH_HDD_1=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-gnome-wicked@%MACHINE%.qcow2
PUBLISH_PFLASH_VARS=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-gnome-wicked@%MACHINE%-uefi-vars.qcow2
START_AFTER_TEST=create_hdd_gnome
UEFI_PFLASH_VARS=%DISTRI%-%VERSION%-%ARCH%-%BUILD%-%DESKTOP%@%MACHINE%-uefi-vars.qcow2
YAML_SCHEDULE=schedule/yast/opensuse/create_hdd_gnome_wicked.yaml
maybe the differing parameters like missing QEMU_COMPRESS_QCOW2 and HDDSIZEGB=20 vs. 40 make a problem. Maybe the easiest way to resolve is to quickly ask owners in irc://libera.chat/opensuse-factory if there are any objections and if not then just change the create_hdd_gnome_wicked" testsuite.
Updated by dheidler 7 months ago
I guess I will try to not modify create_hdd_gnome_wicked, as the HDDSIZEGB=20 there shouldn't even do anything, as it is just reconfiguring a NetworkManager installation to use wicked.
So the HDDSIZEGB=40 would need to be put into create_hdd_gnome which would affect a lot of tests.
As long as I don't run into issues with 20G that is.
Updated by okurz 7 months ago
https://github.com/os-autoinst/scripts/pull/267 merged, https://github.com/os-autoinst/openQA/pull/5332 merged, https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/147 merged. Verification job showing the script not breaking anything in openQA-in-openQA test: https://openqa.opensuse.org/tests/3658269#step/openqa_worker/9
So to be strict you can call ACs covered because the script at least does not break the single-machine use case as ensured by automatic tests. You can now either extend the test to do real multi-machine tests or create a separate ticket about that and resolve here.
Updated by livdywan 7 months ago
- Copied to action #138302: Ensure automated openQA tests verify that os-autoinst-setup-multi-machine sets up valid networking size:M added
Updated by livdywan 7 months ago
- Subject changed from http://open.qa/docs/#_configure_virtual_interfaces instructions do not work on Leap 15.5 size:M to Configure Virtual Interfaces instructions do not work on Leap 15.5 size:M
We discussed the follow-up ticket before, which I filed now so I suggest we wrap it up here if there's no surprises like breakage from the fixes that were merged.
Updated by livdywan 7 months ago
- Related to action #138263: Strip unneeded code from os-autoinst-setup-multi-machine added
Updated by dheidler 7 months ago
- Related to action #138326: Extend openQA-in-openQA test to do a real multimachine run. added
Updated by dheidler 7 months ago
- Related to deleted (action #138326: Extend openQA-in-openQA test to do a real multimachine run.)
Updated by jbaier_cz 6 months ago
- Related to action #126680: [openQA-in-openQA] no candidate needle with tag(s) 'boot-menu, openqa-desktop' matched in worker size:M added