RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1041395 - depsolve_loop_limit 0 does not works as documented
Summary: depsolve_loop_limit 0 does not works as documented
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jan Zeleny
QA Contact: Patrik Kis
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 15:47 UTC by Patrik Kis
Modified: 2014-06-18 05:18 UTC (History)
2 users (show)

Fixed In Version: yum-3.4.3-110.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:55:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.