action #113647
Updated by JERiveraMoya almost 2 years ago
.... draft .... #### Motivation #### Based on research in #113650 we should be able to upgrade SLE-15-SP3 containing latest maintenance updates to SLE-15-SP4 GM. In this ticket we will kick 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. updates: https://openqa.suse.de/tests/9130318 #### 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: Interaction with yast2 migration are done using libyui #### Suggestions 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. 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.