Status update¶
After inserting add_update_test_repo into create_hdd_transactional_server.yaml the following was observed:
- Verification run on SLE15-SP3 worked without any problems.
- Verification run on SLE15-SP2 failed in the next test module which is addon_products_sle
Analysis of the fail in the SLE15-SP2 VR¶
The problem seems to be that SLE15-SP2 does set the checkbox 'I would like to install an additional addon product' but then does not install anything.
The test module addon_products_sle would either accept this page with no checked checkbox or even an overview screen that shows what addon repos are setup already.
Creating an workaround¶
So we have the problem, that the checkbox is checked when nothing is there to be installed. Therefore I patched add_update_test_repo by moving the line that checks the checkbox a bit down and only sending the hotkey if there are repos to be installed.
Code now looks like this:
assert_screen 'inst-addon';
set_var('MAINT_TEST_REPO', get_var('INCIDENT_REPO')) if get_var('INCIDENT_REPO');
my @repos = split(/,/, get_var('MAINT_TEST_REPO'));
send_key 'alt-k' if scalar @repos; # install with a maint update repo
while (defined(my $maintrepo = shift @repos)) {
Verification run on SLE15-SP2 then worked without any problem. Restarting the VR on SLE15-SP3 was a big surprise, because now I got errors in add_update_test_repo that complained that repos could not be created.
Analysis of the problem in the repeated VR on SLE15-SP3¶
Turned out, that the URLs where the test complained really result in an HTTP-404 when I tried to access them in the browser. Looking deeper into this I noticed that the tests in the job group were performed 16 hours ago, while my first VR that I repeated was performed 7 days ago.
In the settings there is a setting BASE_TEST_ISSUES which holds the issue numbers. And the current setting differs from my VR 7 days ago, at least the issue that now the repeated VR (with the 7 days old settings) is no longer in the current settings for this test. Therefore I restarted the VRs based on the latest tests in the job group for SLE15-SP2 and SLE15-SP3.
Looks like those test settings have a dynamic life and repos disappear when the test issue disappears. -> *somebody should explain the maintenance process to us
Back to the SLE15-SP2 issue¶
The remaining question still is: Why are there no repos to be setup for add_update_test_repo?
Looking at the settings it turns out that there is no longer a BASE_TEST_ISSUES setting. The only setting that seems to hold issue numbers is LTSS_TEST_ISSUES. Grepping through the code in os-autoinst-distri-opensuse shows, that this setting is used nowhere.
So my current theory is that the issues were moved to LTSS_TEST_ISSUES once a product goes into LTSS state. Which means that with the current code no repos to install updates from will be setup.