action #154318
closedcoordination #151816: [epic] Handle openQA fixes and job group setup
Update two cases with snapper rollback issue
0%
Description
Motivation¶
Copy the following two cases from migration daily group to migration dev job group to trace the sanpper rollback failure and keep the same test suite but without rollback in its existing job group.
- offline_sles12sp5_media_we-lp_def_full
- offline_sles12sp5_pscc_def_full_lock
*_dev test suite should have a comment in yaml job group pointing to the bug.
Acceptance criteria¶
AC1: Copy the two cases above from migration daily group to migration dev job group
AC2: Remove the setting of ROLLBACK_AFTER_MIGRATION=1 for these two testsuites in daily group
Updated by JERiveraMoya 4 months ago
- Tags set to qe-yam-feb-sprint
- Description updated (diff)
- Status changed from New to Workable
- Parent task set to #151816
We should give a time (1 month?) if there is some activity on bsc#1219173 but in rc phase might expect no action, therefore this test avoid to keep showing testing of this feature in official group.
Updated by tinawang123 4 months ago
- Status changed from Workable to In Progress
- Assignee set to tinawang123
Updated by tinawang123 4 months ago
Updated by JERiveraMoya 4 months ago
- Tags deleted (
qe-yam-feb-sprint) - Status changed from In Progress to New
It becomes P1, so we will not need this most likely. Let's wait.
Please check carefully from which Sprint you pick the ticket, this is another one from February, my idea was to wait, that is why is Feb.
Please reject this ticket when the problem is fixed.
Updated by JERiveraMoya about 1 month ago
- Status changed from New to Rejected
Looks like we can reject this one, reopen if I'm wrong.