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

Motivation¶

In Maintenance testing for aggregate we are testing the interactive installation in some test suite without having in bootloader parameters self_update pointing to a proper maintenance repo. This means that the installer is updated by default and takes the latest package from scc.
For example in this case https://openqa.suse.de/tests/9318039#step/bootloader_start/9
will pull from official channels: https://updates.suse.com/SUSE/Updates/SLE-INSTALLER/15-SP4/x86_64/update/
This mean that we are not testing the latest updates for the installer, so the installer is the same, the screen are the same, the packages that tune your system are the same, there is not need for testing it over and over, it is static.
Once we set the parameter like in here: https://openqa.suse.de/tests/9318044#step/bootloader_start/9 we also will pull the latest from scc plus new updates for the installer itself, so then it make sense to test for example partitioning.
In summary, these scenarios inherited from Core squad missed this logic, there is no point on testing partitioning for every single build (which happen daily) during interactive installation which is using yast-storage-ng if we don't pass that parameters, as we would be testing always the version in scc, or in other words already approved updates.

For quarter updates seems that is option is disabled by default not even connecting to scc to update the installer, makes sense because there GM images are not used, those new images already have newer packages. We are still not there, we don't have yet single-incidents or quarter update maintenance testing, once we have stability with libyui-rest-api in aggregate we plan to tackle those as well.

Acceptance criteria¶

AC1: All the interactive installation in YaST MUs job group have set self_update as bootloader parameter