Project

General

Profile

Actions

action #17042

closed

coordination #15108: [sle][functional][u][epic] Modules (Installation + migration)

[sles][functional][modules] Modules installation

Added by maritawerner about 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
New test
Start date:
2017-02-14
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

goal

Make sure that each module installs correctly.

acceptance criteria

  • AC1: One module is tested on every SLES build using proxy-SCC
  • AC2: Multiple modules are tested

tasks

  • set SCC_ADDONS=<module_name1>[,<module_name2>] accordingly (SCC regurl should only register SLES, not point to any module)
  • after the module(s) are registered and enabled packages should be installed from the modules, e.g. by selecting the appropriate pattern(s)

further details

As SLE service packs and therefore also builds within service packs are meant to be ABI compatible modules can be simply installed over SCC while registering the latest SLES build. For all modules that are already on SCC we just install them over SCC (That's it. No need to sync anything anywhere).
Enabling modules does not install anything from it automatically. patterns or packages need to be selected, e.g. after enabling "hpcm" then "zypper search hpc" should return something. Also the repository can be explicitly selected with "zypper lr" and then all packages and patterns from that repo can be listed with "zypper search -r ".
So far module installation was never done besides textmode during online migration but these are actually "post-validation" tests as described in #15800.


Files

canvas.png (40.2 KB) canvas.png screenshot of openQA test run showing how the repository URLs look like after rewriting okurz, 2017-05-06 07:33
openQA_rewritten_sle_module_paths.png (15.3 KB) openQA_rewritten_sle_module_paths.png okurz, 2017-05-06 09:08
Actions

Also available in: Atom PDF