Project

General

Profile

Actions
Copy link

action #158401

closed

Investigate why YaST MU SLES12SP5 cases (three cases) didn't add MU unreleased repos

Added by zoecao about 1 month ago. Updated 21 days ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2024-04-02
Due date:
% Done:

0%

Estimated time:

Description

Motivation

In YaST MU job group, the SLES12SP5 test cases, for example [create_hdd_yast_maintenance_desktop] case didn't add any MU unreleased repos, please check the output of " [zypper -n ref]" and the uploaded [repo list.log] after installation.
Only SLES12SP5 test cases didn't add MU unreleased repos with the following test cases:
[autoyast_filesystem_withouthome_yast]
[create_hdd_yast_maintenance_desktop]
[create_hdd_yast_maintenance_minimal]
It works fine on the same testuistes on SLES15SPx, for example: https://openqa.suse.de/tests/13921758#step/repos/9
So need to find out why it doesn't work for SLES12SP5, may need to check autoyast profile and testsuites' settings.

Acceptance criteria

AC1 : Investigate why the MU unreleased repos are not added to YaST MU SLES12SP5 test cases (the three cases listed above)
AC2 : Find out the resolution or file bug if necessary.

Actions
Copy link
 #1

Updated by leli 27 days ago

After some investigation, this issue come from setting NO_ADD_MAINT_TEST_REPOS=1 which will cause test won't add unreleased repo.

tests/qa_automation/patch_and_reboot.pm:43: add_test_repositories;

In this function will depend on the setting to add or not add repos.

Actions
Copy link
 #2

Updated by leli 27 days ago

In fact, even with NO_ADD_MAINT_TEST_REPOS=1 the uploaded profile after installation contains the un-released repo which means already added these repo on system. So I think the patch_and_reboot just try to add repos to update, since these repos just added during installation, so no fresh update for them. So no problem to add/not add for these un-released repos during patch_and_reboot.

Actions
Copy link

Also available in: Atom PDF