Move test suite rmt_server_install from 'YaST' to 'Migration: Milestone' job group
While reviewing YaST group on build 21.1, the test suite of rmt_server_install failed for RMT as it can't be mirrored before BETA (https://openqa.nue.suse.com/tests/9527513#step/enable_online_repos/1).
So we decided to move this test suite from 'YaST' to 'Migration: Milestone' job group (it is not a migration, but it is the only place where it fits for now, before further reorganization/merge of jobs groups between YaST and Migration scope.
AC1: Move test suite rmt_server_install from 'YaST' to 'Migration: Milestone' job group
On the contrary, i think this case can be keep yast group with daily triggered, it can check connectivity of rmt from time to time disregard the milestone time slot.
No, I checked the case rmt_server_install in yast group, it is to install a SLES15SP5 via rmt server. In this situation, it is necessary to move the case to milestone group cause the rmt server only mirror milestone builds.
#13 Updated by jgwang about 2 months ago
I created a MR to add "rmt_server_install" into migration milestone group:
and created a MR to delete "rmt_server_install" from YaST group:
#15 Updated by openqa_review about 1 month ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: rmt_server_install
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.