action #49172
closedImplement migration test from same version to the same version (bsc#1128459)
0%
Description
Motivation¶
Inspired by https://bugzilla.suse.com/show_bug.cgi?id=1128459 Some of our customers use this trick to fix the system and recover it from the issues.
It's not common use-case though and is not officially documented, whereas will allow us to catch bugs and identify issues easier, which can be a prerequisite for the actual migration tests.
Updated by okurz over 5 years ago
- Target version set to future
cool idea. Do you think we should move it to "[migration]" instead? I would assume that QSF-y would estimate the effort for this one very high as the team is not very experienced with migration tests?
Updated by riafarov about 4 years ago
- Project changed from openQA Tests (public) to qe-yam
- Subject changed from [functional][y] Implement migration test from same version to the same version (bsc#1128459) to Implement migration test from same version to the same version (bsc#1128459)
- Category deleted (
New test)
Updated by okurz about 3 years ago
- Priority changed from Normal to Low
This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives. The ticket will be set to the next lower priority of "Low" as discussed with qe-yast PO oorlov (https://suse.slack.com/archives/C02LECV2R0X/p1636974668013200)