Project

General

Profile

Actions

action #23438

closed

coordination #20580: [sle][functional][epic] sle 15 setup

[sle][functional][sle15] decide how and start using SCC using SUSEConnect

Added by riafarov over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Target version:
-
Start date:
2017-08-17
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Recently, SCC team has provided a way how SCC can be used, see https://etherpad.nue.suse.com/leanos-activation

At the moment, we don't have working proxy scc and using repos provided by SCC can be used only as a short term solution.

What is required in long term is to adjust proxy SCC (seems that . in build name is not expected), so we use local repos available on osd.
After that we need to adjust rsync.pl to provide correct SCC_URL.

As we already have temporary workaround for installation we need to decide if we should do this before product selection is even possible, along with adding proxy scc url.


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #23506: [sle][functional]test fails in addon_products_sle, trying to continue with empty regcodeResolvedokurz2017-08-25

Actions
Actions #1

Updated by riafarov over 6 years ago

After doing some experiments, we continue using existing workarounds. We have introduced changes to proxy scc, so now it's capable of handling versions with dot (as we have for sle15), so we can adjust tests to register. Rsync script requires adjustments to pass proper value for SCC_URL variable.

Actions #2

Updated by okurz over 6 years ago

  • Category set to New test

Before you adjust openQA tests I suggest to test manually using SUSEConnect which also takes a custom URL so it can as easy as a docker image as described on https://github.com/SUSE/scc-qa-proxy#trying-it-out-with-docker

Actions #3

Updated by riafarov over 6 years ago

@okurz Sure, I'll try both manually first, real build during installation and then using tool. As there was a problem with license for base module.

Actions #4

Updated by riafarov over 6 years ago

  • Related to action #23506: [sle][functional]test fails in addon_products_sle, trying to continue with empty regcode added
Actions #5

Updated by riafarov over 6 years ago

  • Status changed from New to Resolved

As of now we continue using our workaround and supply addons manually. Once functionality works for x86_64, we can adjust medium settings. Proxy scc was adjusted to support dots in build name. Url may look like: SCC_URL=http://Module-SERVER-Applications-%BUILD%.Module-Development-%BUILD%.Module-Scripting-%BUILD%.Module-Legacy-%BUILD%.Module-DESKTOP-Applications-%BUILD%.Module-Basesystem-%BUILD%.Leanos-%BUILD%.proxy.scc.suse.de

Actions

Also available in: Atom PDF