Project

General

Profile

action #116365

Updated by JERiveraMoya over 1 year ago

#### Motivation 
 See #109187 
 It is done for SLE-15-SP{3,4} in #109214. Let's try to reuse the same AutoYaST profile for the rest of the products in maintenance. 
 [mru-install-desktop-with-addons](https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=mru-install-desktop-with-addons&modules=&module_re=&distri=sle&version=12-SP4&version=12-SP5&build=20220907-1&groupid=414#) | [mru-install-minimal-with-addons](https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=mru-install-minimal-with-addons&modules=&module_re=&distri=sle&version=12-SP4&version=12-SP5&build=20220907-1&groupid=414#) 

 These new testsuites should be put in YaST Development job group. Then we will file another ticket to deploy this in YaST MU job group. 

 #### Scope 
 Test suites with external dependencies: `mru-install-desktop-with-addons` & `mru-install-minimal-with-addons` 
 Products:    SLE 12-SP4 and SLE 12-SP5. 
 Architectures: `mru-install-minimal-with-addons` is running in three architectures, aim for all of them if possible. 

 #### Acceptance criteria 
 **AC1**: New AutoYaST test suites are created in 'YaST Maintenance Updates - Development' openQA job group corresponding to `mru-install-desktop-with-addons` & `mru-install-minimal-with-addons`. 
 **AC2**: Copies of the chained dependencies of test suites `mru-install-desktop-with-addons` & `mru-install-minimal-with-addons` which are in YaST MU job group will be set to new AutoYaST test suites in 'YaST Maintenance Updates - Development' job group 
 **AC3**: If we cannot reuse the AutoYaST profile created for SLE-15-SP{3,4} consider to reduce the scope of products or architectures to migrate to AutoYaST. 

 #### Suggestions 
 * Reuse knowledge from previous task: #107674 #109187 
 * We could reuse very likely the AutoYaST profiles created for SLE-15-SP3. 
 * Rename the teststuites creating AutoYaST image to `autoyast_create_*` so we can distinguish better between old and new things regardless of the job group, maintenance or product. 

 For sle-12-sp5 seems that we can reuse the profile, but for sle-12-sp4 where we have some issue with ltss we need to figure out.

Back