action #113647
Updated by JERiveraMoya over 1 year ago
#### Motivation #### Based on research in #113650 we should be able to upgrade SLE-15-SP3 containing latest maintenance updates to SLE-15-SP4 (SCC without MUs) GM. In this ticket we will kick off the upgrade process for Maintenance updates. The simplest path is to migrate between 2 versions of the product in maintenance that are closed to each other, in this case SLE-15-SP3 and SLE-15-SP4. We will start from the path which go from unofficial channels to official ones. We will be using some minimal system, we have available for SLE-15-SP3 image already patched with maintenance updates created by this job: [create_hdd_yast_maintenance_minimal](https://openqa.suse.de/tests/9176653) As the research shows, there was some issues with this image, YaST migration detects that there are not product installed, check research ticket for more info. So in case this problem is not solved we can use [mru-install-minimal-with-addons](https://openqa.suse.de/tests/9176667) which works just fine. #### Acceptance criteria #### **AC1**: New test suite where we proceed with migration using YaST module is added to SLE-15-SP3 in YaST MUs - Development **AC2**: This test suite is chained with existing attended or unattended (pick the one that works) installation. ~~**AC3**: **AC3**: Interaction with yast2 migration are done using libyui~~ (let's keep it simple for now) libyui #### Suggestions #### ~~Instead Instead of implementing layers of testing for libyui REST Test -> Controller -> Page, let's simplify development and declare Pages at the level of test, the page will have the UI controls mapped as usual, but there is not need for controller or to use a Distribution pattern. Later on we can think if we need for some cases that complexity.~~ (let's keep it simple for now) complexity. We can skip additional checks and decide in other ticket what exactly we want to add. For example we see here in this example pre_migration, etc. https://openqa.suse.de/tests/8753537 Let's do the basic here only. [Here](https://openqa.suse.de/tests/8753540#step/yast2_migration/2) we can see how the YaST module perform the migration using SLE-15-SP3 (not SLE-15-SP4 as initially we thought, so the AutoYaST job should work, see [bsc#1201698](https://bugzilla.suse.com/show_bug.cgi?id=1201698) During the ticket development it was decided to go for the offline migration as we can change the ISO. This one is the one expected to be delivered.