action #42227
Updated by riafarov over 6 years ago
See motivation in the parent ticket ## Acceptance criteria 1. Relevant scenarios are moved to YaST job group 2. All performed changes are documented 3. Setup is backed up before the changes ## Here is the list of identified scenarios to be moved as they are currently are in Functional job group: * RAID0/1/10/5/6 * addon-module-ftp * addon-module-http * allmodules+allpatterns * btrfs * btrfs+warnings (use EXIT_AFTER_START_INSTALL) * clone_system * create_hdd_gnome * create_hdd_sled_gnome@64bit-virtio-vga * create_hdd_textmode * crypt_no_lvm * cryptlvm+activate_existing * cryptlvm+activate_existing+force_recompute * cryptlvm+activate_existing+import_users * cryptlvm+cancel_existing * detect_yast2_failures * dud_development_tools * ext4 * gnome_http * gnome_install_smt ? (we don't own smt) * gnome_self_signed_https * gnome_smb * gpt (no sense to run on SLE15, default there, covered) * installer_extended (we can cover it in detect_yast2_failures, as of now this test suite doesn't make any sense) * iscsi_client * iscsi_server * lvm+RAID1 * lvm+cancel_existing_cryptlvm * lvm-encrypt-separate-boot * minimal+base * minimal+role_minimal * multipath * nis_client * nis_server * nvme * registered+gnome+dev_tools_all_packages_dvd * releasenotes_origin+unregistered * remote_ssh_controller * remote_ssh_target_ftp * remote_vnc_controller * remote_vnc_target_nfs * select_disk * skip_registration * sles+sdk+proxy_SCC_via_YaST * switch_keyboard_gnome * switch_keyboard_textmode * xfs * yast2_gui * yast2_ncurses * yast2_ui_devel * yast_hostname * yast_hostname+dhcp_hostname * yast_hostname+linuxrc_hostname * yast_no_self_update * yast_self_update * zfcp@s390x-zfcp