action #17042

Updated by okurz almost 3 years ago

## 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
* sync a module manually under todays date as fake build number and then specificy that build number as part of the scc url
* set `SCC_ADDONS=<module_name1>[,<module_name2>]` and SCC regurl accordingly
* extend openqa-scripts to do the syncing automatically on a daily basis
* 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

To properly test module usage we need to use proxy-SCC to get the modules into the system. As we want to test products before release we need to sync all modules repositories to be tested to osd and use the proxy-SCC URL to reference the base product as well as all modules to be installed as described on https://github.com/SUSE/scc-qa-proxy .
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 <nr_of_repo>".
So far module installation was never done besides textmode during online migration but these are actually "post-validation" tests as described in #15800.

As modules change on a different pace to products we should sync modules every morning from a different script with a part like `latest_addon` within rsync.pl or do the sync on demand but have rsync.pl reference the latest there is.

This description is based on #12908#note-4
corretly.

Back