action #119878
closedcoordination #119836: [epic] Convert YAML schedules for YaST to be based on YAML default files
Adapt default yaml file for s390x KVM and test suites to use it in YaST group
Description
Observation¶
As follow-up of #115319 where we applied a default file to fix a couple of test suites, in this ticket we should modify this default file (if needed) to be used with the rest of test suite running in architecture s390x and backend KVM.
This is the list of jobs:
https://openqa.suse.de/tests/overview?arch=&flavor=&machine=s390x-kvm-sle12&test=&modules=&module_re=&distri=sle&version=15-SP5&build=32.1&groupid=129#
This is the list of test suites in case the link would get outdated:
-
select_modules_and_patterns+registration
-
textmode_installation_minimal_role
-
addon_extensions_http_ftp
-
autoyast_reinstall
-
btrfs+warnings
-
clone_system
-
create_hdd_gnome_libyui
-
create_hdd_transactional_server
-
guided_btrfs
-
guided_ext4
-
guided_xfs
-
installer_extended
-
lvm-encrypt-separate-boot
-
lvm-full-encrypt
-
lvm_thin_provisioning
-
minimal+base_yast
-
minimal+role_minimal
-
modify_existing_partition
-
msdos
-
select_modules_and_patterns
-
textmode
-
transactional_server_helper_apps
-
transactional_server_snapper
-
yast2_cmd
-
yast2_gui
-
yast2_ncurses_gnome
-
yast2_ncurses_textmode
-
yast_no_self_update
-
yast_self_update
Acceptance criteria¶
AC1: Adapt default yaml file for s390x KVM which can work with all the test suite listed above
AC2: Modify only schedules for s390x KVM to make them work with its corresponding default yaml
Suggestions¶
- If one schedule is used for several architecture, rather than modify it, we can create a new schedule file for now to use keys instead of list of modules.
- Take inspiration from #115319
- For now there is not much thought about how the solution would work for test suites after installation, so let's focus on installation and consider the the other test suite, if it feasible we can try out, otherwise file a ticket for them.