action #122020
closedcoordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5
Try if spvm console can help with the sporadic issues found for PowerVM
Description
Motivation¶
Yam squad in YaST group hits this infrastructure issue: #117808 and apparently there is not expected progress to update that old grub version to make testing more stable. Anyway IBM is testing on its own SLES, and we don't have configured an environment that mimics better how this virtualization is tested.
The goal of this ticket is to leave just one PowerVM job in YaST job group to review more frecuently and move the rest of the jobs to YaST development group.
Before sending new Milestone report Yam squad will check for results in Development group and certain openQA will be applied on that development job group to not miss any bug, but no so frequent or formal like intermediate snapshots or milestones.
Previously we tried to chained jobs to avoid scheduling but it didn't work so well.
Acceptance criteria¶
AC1: Leave only one PowerVM test suite running in YaST job group (excluding flaky tests from having more often review)
AC2: Label properly the failures with corresponding ticket in YaST Development job group.
AC1: Run with backend spvm at least 5 times per each test suite, test suites currently running with backend pvm_hmc and see if we don't hit the bug.
Suggestion¶
guided_btrfs (see here https://openqa.suse.de/tests/10088041#dependencies) is a good candidate to keep in Online medium.
For full flavor we can move them all.