action #23492
closed
coordination #20580: [sle][functional][epic] sle 15 setup
[sle][functional]test fails in scc_registration - openQA SLE media are missing SCC_URL
Added by okurz over 7 years ago.
Updated over 7 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-Leanos-DVD-x86_64-gnome+proxy_SCC+allmodules@64bit fails in
scc_registration
Reproducible¶
Fails since (at least) Build 93.17
Expected result¶
Last good: Compare to SLE 12 SP3
Further details¶
Always latest result in this scenario: latest
- Parent task set to #20580
- Related to action #23506: [sle][functional]test fails in addon_products_sle, trying to continue with empty regcode added
- Priority changed from Normal to Urgent
Since this is the basic feature of a sle installation and this test shows how far we can get in the installation
Proxy SCC now works during installation, so we can adjust this testsuite first and then use it for other test suites to select modules during installation.
- Status changed from New to In Progress
What do you mean with "add the variables"? This should be handled by the existing variable which enables all modules in this test suite. Also we should not add the reg url to the test suite but the version specific medium, right? Regarding other scenarios when we need as a workaround to explicitly enable modules to resemble what should be auto-selected for SLES I suggest to do that as well in the test code, not openQA settings.
- Due date set to 2017-09-27
both PR and needles merged
- Status changed from In Progress to Resolved
The actual SCC_URL we put on the media on https://openqa.suse.de/admin/products is SCC_URL=http://Module-Server-Applications-%BUILD%.Module-Development-Tools-%BUILD%.Module-Scripting-%BUILD%.Module-Legacy-%BUILD%.Module-Desktop-Applications-%BUILD%.Module-Basesystem-%BUILD%.proxy.scc.suse.de
so no capital case names. The additional benefit of using the same %BUILD%
within each component is that in case of any module syncing mismatch the tests should fail early e.g. when trying to access the module repos after SCC registration which is better than a later "package not found" error or an incomplete job failing to find an ISO medium.
I guess we are done here, validation sle-15-Leanos-DVD-x86_64-Build248.1-gnome+proxy_SCC+allmodules@64bit
Also available in: Atom
PDF