Project

General

Profile

action #33184

Updated by okurz over 5 years ago

## Observation 

 openQA test in scenario sle-12-SP4-Server-DVD-x86_64-extra_tests_in_textmode@64bit fails in 
 [docker](https://openqa.suse.de/tests/1536203/modules/docker/steps/6) 


 ## Reproducible 

 Fails since (at least) Build [0095](https://openqa.suse.de/tests/1332451) 


 ## Suggestions Further details 

 * Schedule the docker module Always latest result in the "proxy_SCC+allmodules" scenario this scenario: [latest](https://openqa.suse.de/tests/latest?flavor=Server-DVD&test=extra_tests_in_textmode&arch=x86_64&machine=64bit&version=12-SP4&distri=sle) 


 ## Tasks to be done 

 - Set a test suite **create_hdd_textmode_registered** for SLE12 product validation and not in extra_tests_in_textmode 
 * Ensure the module is still scheduled for maintenance SLE12-SP5, to be able to run tests with a registered system. 
 * Ensure the module is still scheduled as "extra_tests" - Set a test suite **extra_tests_textmode_registered** for SLE15 SLE12-SP5, to be able to run docker tests. 
 * - Remove the hack from https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/e70ba1caa4403c93f230ed94279c0971d7f8f933/lib/registration.pm#L671 to not add a repo, but installing docker from the proper repository. 


 ## Further details 

 Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?flavor=Server-DVD&test=extra_tests_in_textmode&arch=x86_64&machine=64bit&version=12-SP4&distri=sle) 

 ### Reasoning for the current suggestions 

 The modules within SLE12 are developed and maintained separately from SLES using the maintenance process. Therefore we also use the module content of publically published repos and not any internal copy which is not developed in sync with any build of SLES anyway. Therefore we need to select a different approach than for SLE15 anyway. We already do that approach within "proxy_SCC+allmodules", e.g. for "puppet" or "salt" from ASMM. Publishing a "registered" image could mislead us to think that the module content would be consistent with the build of SLES12 but there is no hard relation between the both.

Back