Actions
action #164592
closed[qem][qe-core][leap]test fails in install_packages, new packages can't be handled
Start date:
2024-07-29
Due date:
% Done:
0%
Estimated time:
Difficulty:
Tags:
Description
Description¶
See more detail information at https://suse.slack.com/archives/C02CSAZLAR4/p1722244465417869
Current test module seems can't handle new packages like below:
rsh/rsh-server are new packages which are requested. however, we can't get the packages in leap online repos.
Force installation of the packages are fine:
susetest:~ # zypper in rsh rsh-server
Reading installed packages...
Resolving package dependencies...
2 Problems:
Problem: 1: the installed mrsh-rsh-compat-2.12-4.3.1.x86_64 conflicts with 'namespace:otherproviders(rsh)' provided by the to be installed rsh-0.17-bp155.2.1.x86_64
Problem: 2: the installed mrsh-rsh-server-compat-2.12-4.3.1.x86_64 conflicts with 'namespace:otherproviders(rsh-server)' provided by the to be installed rsh-server-0.17-bp155.2.1.x86_64
Problem: 1: the installed mrsh-rsh-compat-2.12-4.3.1.x86_64 conflicts with 'namespace:otherproviders(rsh)' provided by the to be installed rsh-0.17-bp155.2.1.x86_64
Solution 1: deinstallation of mrsh-rsh-compat-2.12-4.3.1.x86_64
Solution 2: do not install rsh-0.17-bp155.2.1.x86_64
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): 1
Problem: 2: the installed mrsh-rsh-server-compat-2.12-4.3.1.x86_64 conflicts with 'namespace:otherproviders(rsh-server)' provided by the to be installed rsh-server-0.17-bp155.2.1.x86_64
Solution 1: deinstallation of mrsh-rsh-server-compat-2.12-4.3.1.x86_64
Solution 2: do not install rsh-server-0.17-bp155.2.1.x86_64
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): 1
Resolving dependencies...
Resolving package dependencies...
The following 2 NEW packages are going to be installed:
rsh rsh-server
The following 2 packages are going to be REMOVED:
mrsh-rsh-compat mrsh-rsh-server-compat
2 new packages to install, 2 to remove.
Overall download size: 90.2 KiB. Already cached: 0 B. After the operation, additional 204.7 KiB will be used.
Current logic is still trying to install the non-existing packages [may be older versions] before applying the patch. then it fails:
#~lsmfip --verbose rsh rsh-server $XDG_RUNTIME_DIR/install_packages.txt 2> /tmp/lsmfip.log
# cat /tmp/lsmfip.log
adding repo @System
adding repo openSUSE-Leap-15.5-1
adding repo repo-backports-update
adding repo repo-non-oss
adding repo repo-openh264
adding repo repo-oss
adding repo repo-sle-update
adding repo repo-update
adding repo repo-update-non-oss
selecting rsh
INSTALL rsh
selecting rsh-server
INSTALL rsh-server
rsh-server was requested but nothing was installed at /home/bernhard/data/lsmfip line 295.
However, zypper command to install the packages doesn't hit any issue.
susetest:/home/bernhard/bin # zypper in rsh rsh-server
Loading repository data...
Warning: Repository 'untrusted0' metadata expired since 2023-10-22 08:20:50 EDT.
Warning: Repository 'untrusted1' metadata expired since 2024-06-10 07:54:58 EDT.
Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise
manually refresh the repository (zypper ref). If this does not solve the issue, it could be that
you are using a broken mirror or the server has actually discontinued to support the repository.
Reading installed packages...
'rsh' not found in package names. Trying capabilities.
'mrsh-rsh-compat' providing 'rsh' is already installed.
'rsh-server' not found in package names. Trying capabilities.
'mrsh-rsh-server-compat' providing 'rsh-server' is already installed.
Resolving package dependencies...
Nothing to do.
susetest:/home/bernhard/bin # echo $?
0
Observation¶
openQA test in scenario opensuse-15.5-DVD-Backports-Incidents-x86_64-install_with_updates_gnome@64bit-2G fails in
install_packages
Action items¶
- [option] Enhance the logic of
lsmfip
binary to handle new packges - Use the similar logic as OSD QAM tests do update_install
- We may need to handle qam_zypper_patch as well, since 'zypper in -l -t patch' does nothing for new packges IMO, see link
Test suite description¶
Reproducible¶
Fails since (at least) Build :18385:rsh.1721121848 (current job)
Expected result¶
Last good: 20240716-3 (or more recent)
Further details¶
Always latest result in this scenario: latest
Actions