action #33184
closed[sle][functional][12sp4][u]test fails in docker - needs to add container module / how do we want to execute extra tests that rely on a registered image for SLE12?
0%
Description
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-x86_64-extra_tests_in_textmode@64bit fails in
docker
Reproducible¶
Fails since (at least) Build 0095
Suggestions¶
- Schedule the docker module in the "proxy_SCC+allmodules" scenario for SLE12 product validation and not in extra_tests_in_textmode
- Ensure the module is still scheduled for maintenance tests
- Ensure the module is still scheduled as "extra_tests" for SLE15
- 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
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.