Project

General

Profile

action #119587

Updated by JERiveraMoya over 1 year ago

#### ## Observation 

 openQA test in scenario sle-15-SP5-Full-s390x-select_modules_and_patterns+registration@s390x-zVM-vswitch-l3 fails in 
 As follow-up of #115319 we didn't notice [accept_license](https://openqa.suse.de/tests/9842454/modules/accept_license/steps/2) 

 ## Test suite description 
   Full Medium installation that for s390x zVM covers the same problem occurred because jobs didn't run following cases: 
      1. Additional modules enabled using SCC (Legacy, Development Tools, 
         Web and Scripting, Containers, Desktop Applications); 
      2. Yast patterns installed; 
      3. System registration is skipped during installation; 
      4. Installation is validated by successful boot and that YaST does not 
         report any issues; 
      5. Registration is performed on that time due to parent dependency. 
 These are the new failures found: 
 https://openqa.suse.de/tests/9842453#step/accept_license/2 
 https://openqa.suse.de/tests/9842454#step/accept_license/2 installed system. 


 ## Reproducible 

 We don't want to target only those failures Fails since (at least) Build [32.1](https://openqa.suse.de/tests/9831189) 


 ## Expected result 

 Last good: (unknown) (or more recent) 


 ## Further details 

 Always latest result in this ticket but start to craft a default file for the whole arch/backend. scenario: [latest](https://openqa.suse.de/tests/latest?arch=s390x&distri=sle&flavor=Full&machine=s390x-zVM-vswitch-l3&test=select_modules_and_patterns%2Bregistration&version=15-SP5) 
 This is the list of jobs: 
 https://openqa.suse.de/tests/overview?arch=&flavor=&machine=s390x-zVM-vswitch-l2%2Cs390x-zVM-vswitch-l3&test=&modules=&module_re=&distri=sle&version=15-SP5&build=32.1&groupid=129# 
 This is the list of test suites in case the link would get outdated: 
 - select_modules_and_patterns+registration@s390x-zVM-vswitch-l2 
 - select_modules_and_patterns+registration@s390x-zVM-vswitch-l3 
 - autoyast_zvm_sles_product_reg@s390x-zVM-vswitch-l2 
 - guided_btrfs@s390x-zVM-vswitch-l2 
 - guided_btrfs@s390x-zVM-vswitch-l3 
 - guided_ext4@s390x-zVM-vswitch-l3 
 - guided_xfs@s390x-zVM-vswitch-l3 
 - minimal+base_yast@s390x-zVM-vswitch-l3 
 - ssh-X@s390x-zVM-vswitch-l3 
 - textmode@s390x-zVM-vswitch-l3 

 #### Acceptance criteria 
 **AC1**: Create a default yaml file for s390x zkvm which can work with all the test suite listed above 
 **AC2**: Modify only schedules for s390x zkvm to make them work with new created default 

 #### Suggestions 
 - If one schedule is used for several architecture, rather than modify, we can create a new schedule file for now to use keys instead of list of modules. 
 - Take inspiration from #115319 

Back