coordination #152771
Updated by JERiveraMoya 5 months ago
#### Motivation #### Follow-up of #113644 Due to we don't have technically the possibility to add both unreleased maintenance updates from both the origin product to migrate and the target product at the same time we can choose whatever fits better for us, one or the other. Based on this reason we should reuse the installations that we have for each product where we are already adding those unreleased maintenance updates to be tested. We would just need to publish an image for the new migration test suite to consume. It is legit create the dependency due to priority of the migrations is secondary. #### Scope - From SLES 12 SP5 To SLES 15 SP{1,4}. - From SLES 15 SP1 To SLES 15 SP{2,4}. - From SLES 15 SP2 To SLES 15 SP{3,4}. - From SLES 15 SP3 To SLES 15 SP4. - From SLES 12 SP5 To SLES 15 SP5. - From SLES 12 SP5 To SLES 15 SP5. - From SLES 12 SP5 To SLES 15 SP5. - From SLES 12 SP5 To SLES 15 SP5. #### Scope #### All products in maintenance. #### Acceptance criteria #### **AC1**: Migrations Basic set of test suites where upgrade to SP4 is performed is provided for each product in maintenance are provided. **AC2**: Favor stability using refactored test modules and existing libyui-rest-api test modules #### Suggestions #### SLE-15-SP4 could first candidate due to enable this migration. it is more similar to SP5 and might bring more stable test scenario. Analysis by Heiko about the different possibilities: https://confluence.suse.com/display/~hrommel1/Blue-Print+of+Online+Migration+Tests+Between+Two+Service+Packs+in+Maintenance