QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

Motivation¶

It is possible to add those many repositories for the Maintenance Updates using a Driver Update Disk (DUD). In Product validation we have an example of the creation of this DUD by one job and its use by another job:
generate_dud
dud_development_tools

When tested manually with SLE-15-SP4 all those updates were visible in one popup and can be added to the installation, also those repos are visible when inspecting Software -> Details -> repositories in Installation Settings. Installation is able to finish.
Another motivation is the 40 minutes required to add one by one with needles, which can be drastically reduced, perhaps to ~ 5 minutes.

The way we test those maintenance updates using so many repositories is a bit strange, but I guess it has its advantage, so we might use this also no-so-conventional approach to testing. Nevertheless we should have as well the option to add the repos iteratively during installation (see #113731), in case we would want to fall back to this solution for some reason, some bug in the dud mechanism, or perhaps because of its insecure nature. But anyway we are in a testing environment and it might be very useful as you can see.

Scope¶

SLE-15-SP{3,4}, where we can use libyui REST, but we can start applying only to one test suite for example.

Acceptance criteria¶

AC1: New test suite creating DUD is added to YaST MUs - Dev
AC2: Test suite for creation is chained to test suite of your choice using full libyui REST
AC3: An equivalent test module to installation/dud_addon using libyui REST API is created.

Suggestions¶

A test suite of your choice means that we can use any of the test suites adding those repos and replacing their modules by equivalent libyui REST ones, and of course all should happen in openQA job group YaST MUs - Dev.

Troubleshooting: there is a problem after install, some kernel error faced during manual testing in the first boot after install. It was solved just adding all the product modules. It might happen that if there are updates added as repos and not the product module relative to those update, even if the installation can be performed something might get in some inconsistent state.