action #108692
Updated by szarate about 2 years ago
Hello team,
this is a conclusion that we came up with Fabian and Santi in https://bugzilla.opensuse.org/show_bug.cgi?id=1196549
We as a community seem to see a value in keeping even unsupported migration scenarios. Migration over several releases seem to be highly appreciated by community and helps to advertise that we're a rock solid distro that doesn't go through rapid changes.
https://en.opensuse.org/SDB:System_upgrade recommends that user of 15.2 should always migrate to 15.3 prior he migrates to 15.4. However that's not what our migration suite does. We're migrating from let's say 15.0 directly to 15.4 and this has stopped working with 15.3 as we did implement a gpg key loopkup in /repodata which was released as maintenance update to I believe SP2/SP3 but not to older releases as they were EOL.
This request is to ensure that we do migrations without skipping the releases, or migrate at least to 15.2 + full updates first (at that point in time systems were able to migrate to 15.3 which is where the issue has started to appear)
I have to admit that it's quite expensive effort as we keep testing migration scenarios from 42.3 to the recent 15.4.
But it has to be done otherwise we can't get over boo#1196549 and there would be no longer a reason to keep broken test migration test suites.
Thank you
## Acceptance Criteria
1. Migration tests are created for the different combinations, ending in an upgrade to 15.4
## Remarks
* gnome, kde, cryptlvm need those 4 upgrade tests
* 15.0 -> 15.1 -> 15.2 -> 15.3 -> 15.4
* 15.1 -> 15.2 -> 15.3 -> 15.4
* 15.2 -> 15.3 -> 15.4
* 15.3 -> 15.4
Meaning effectively 5 upgrade jobs where all can be chained one to another