action #111231
Updated by JERiveraMoya almost 2 years ago
#### Motivation SLE-15-SP4 GMC is out and problem with maximum of serial consoles [poo#97745](https://progress.opensuse.org/issues/97745) has persisted during the whole Service Pack. Our scope in YaST squad is the installation for sure, and additionally try to validate those installation with some check. This second part is not possible while this problem is there for svirt-hyperv, waiting for the virtualization team fix it or from other squads to contribute, due there was mentioned some issues with priorities. The following jobs has this issue in YaST group: https://openqa.suse.de/tests/overview?arch=&flavor=&machine=svirt-hyperv%2Csvirt-hyperv-uefi&test=&modules=&module_re=&modules_result=failed&distri=sle&version=15-SP4&build=151.1&groupid=129# - select_modules_and_patterns+registration@svirt-hyperv - select_modules_and_patterns+registration@svirt-hyperv-uefi - lvm+RAID1@svirt-hyperv - lvm+RAID1@svirt-hyperv-uefi - minimal+base_yast@svirt-hyperv - minimal+base_yast@svirt-hyperv-uefi - msdos@svirt-hyperv In general this virtualization is pretty slow and the problem is not going to be fixed any time soon, so we can simplify our review process. #### Acceptance criteria **AC1**: Remove validation from test suites above only for svirt-hyperv. **AC2**: Keep at least one of the failure visible and labeled in Development group. ### Suggestions Probably we should not add conditional schedule in existing yaml schedules, but duplicate those files for now. In future we can see how the recently developed yaml flows could play a role here, i.e. a flow with the name of the progress ticket which clear the validations? right now all the flows are overriden by the schedule file, but just some ideas to think about it :)