action #66967
Updated by JERiveraMoya over 4 years ago
So for some of the scenarios below we have some special settings, which can be reused for multiple test suites. In braces we have settings which are different and prevents from complete removal of the test suite from openQA DB List of the scenarios: autoyast_bug-872532_ix64ph1069 (HDDMODEL: scsi-hd) autoyast_bug-876411_btrfs_h5_autoinst (HDDMODEL: scsi-hd) autoyast_bug-877438_ix64ph1029 (HDDMODEL: scsi-hd) autoyast_bug-879147_autoinst (HDDMODEL: scsi-hd) autoyast_bug-887126_autoinst (HDDMODEL: scsi-hd) autoyast_bug-887653_autoinst_jy-snapshot (HDDMODEL: scsi-hd) autoyast_error_dialog autoyast_ext4 autoyast_gnome autoyast_keyboard_layout (HDDMODEL: scsi-hd HDDSIZEGB: '30') autoyast_mini (HDDMODEL: scsi-hd HDDSIZEGB: '30') autoyast_multi_btrfs (NUMDISKS: 4) autoyast_multipath (MULTIPATH) multipath (MULTIPATH) autoyast_non_secure_boot (UEFI_PFLASH_CODE, UEFI_PFLASH_VARS) autoyast_salt (HDDMODEL: scsi-hd HDDSIZEGB: '30') autoyast_zkvm_sles_product_reg btrfs+warnings btrfs_libstorage-ng (HDDSIZEGB) crypt_no_lvm (used by qam) cryptlvm+activate_existing (HDD_1, BOOTFROM) cryptlvm+activate_existing+force_recompute (HDD_1, BOOTFROM) cryptlvm+activate_existing+import_users (HDD_1, BOOTFROM) cryptlvm+cancel_existing (HDD_1, BOOTFROM) lvm+cancel_existing_cryptlvm (HDD_1, BOOTFROM) detect_yast2_failures dud_development_tools ext4_yast (used by qam) gnome_http gnome_self_signed_https gnome_smb installer_extended lvm lvm+RAID1 (HDDSIZEGB) lvm+resize_root (HDDSIZEGB) lvm-encrypt-separate-boot lvm-full-encrypt (HDDSIZEGB) lvm_thin_provisioning (HDDSIZEGB) mediacheck minimal+role_minimal releasenotes_origin+unregistered repo_inst textmode_installation_minimal_role xfs yast_hostname yast_hostname+dhcp_hostname yast_hostname+linuxrc_hostname yast_no_self_update yast_self_update zfcp