Bug 1041395

Summary: depsolve_loop_limit 0 does not works as documented
Product: Red Hat Enterprise Linux 7 Reporter: Patrik Kis <pkis>
Component: yumAssignee: Jan Zeleny <jzeleny>
Status: CLOSED CURRENTRELEASE QA Contact: Patrik Kis <pkis>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: james.antill, jzeleny
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: yum-3.4.3-110.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 09:55:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Patrik Kis 2013-12-12 15:47:10 UTC
Description of problem:
depsolve_loop_limit 0 or "forever" should mean that depsolver will executed forever until resolves all dependencies, but in fact it causes that depsolver exits immediately.
depsolve_loop_limit 1 does not works too as expected.
Moreover, the yum.cons man page is not correct; it says "forever" as a keywork can be used, but it is not accepted by yum. "<forever>" is the correct keyword.


More details can be fond in bug 1038299.

Version-Release number of selected component (if applicable):
yum-3.4.3-106.2.el7

How reproducible:
always

Steps to Reproduce:
0 [root@rhel7 ~ ]# grep depsolv /etc/yum.conf 
depsolve_loop_limit=2
0 [root@rhel7 ~ ]# yum install ksh
Loaded plugins: auto-update-debuginfo, product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
--> Running transaction check
---> Package ksh.x86_64 0:20120801-11.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package       Arch             Version                   Repository       Size
================================================================================
Installing:
 ksh           x86_64           20120801-11.el7           rhel7           874 k

Transaction Summary
================================================================================


Install  1 Package

Total download size: 874 k
Installed size: 3.1 M
Is this ok [y/d/N]: n
Exiting on user command
Your transaction was saved, rerun it with:
 yum load-transaction /tmp/yum_save_tx.2013-12-12.16-42.VOWqKV.yumtx
1 [root@rhel7 ~ ]# 
1 [root@rhel7 ~ ]# sed -i 's/depsolve_loop_limit.*/depsolve_loop_limit=1/' /etc/yum.conf
0 [root@rhel7 ~ ]# yum install ksh
Loaded plugins: auto-update-debuginfo, product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.    
Resolving Dependencies
--> Running transaction check
---> Package ksh.x86_64 0:20120801-11.el7 will be installed
--> Running transaction check
Error: Depsolving loop limit reached.
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
1 [root@rhel7 ~ ]# sed -i 's/depsolve_loop_limit.*/depsolve_loop_limit=0/' /etc/yum.conf
0 [root@rhel7 ~ ]# yum install ksh
Loaded plugins: auto-update-debuginfo, product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
Error: Depsolving loop limit reached.
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
1 [root@rhel7 ~ ]#

Comment 3 Zdeněk Pavlas 2013-12-13 10:28:43 UTC
Fixed upstream.

commit 57f063c11cc8712ce8055d9e9429d897d7d0072c
Author: Zdenek Pavlas <zpavlas>
Date:   Thu Dec 12 10:32:49 2013 +0100

    Test depsolve_loop_count vs depsolve_loop_limit only once

commit cfd0f0f8ad4bb285755ecc66e528a807f864b4ca
Author: Zdenek Pavlas <zpavlas>
Date:   Wed Dec 11 15:09:28 2013 +0100

    depsolve_loop_limit=<forever> should try forever

Comment 7 Ludek Smid 2014-06-13 09:55:55 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.