Bug 1006045 - yum-rhn-plugin should keep its higher default timeout
Summary: yum-rhn-plugin should keep its higher default timeout
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum-rhn-plugin
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stephen Herr
QA Contact: Dimitar Yordanov
URL:
Whiteboard:
Depends On: 1006037
Blocks: 1082754
TreeView+ depends on / blocked
 
Reported: 2013-09-09 21:15 UTC by Stephen Herr
Modified: 2015-03-05 10:52 UTC (History)
3 users (show)

Fixed In Version: yum-rhn-plugin-2.0.1-2-el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1006037
Environment:
Last Closed: 2015-03-05 10:52:02 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0473 0 normal SHIPPED_LIVE yum-rhn-plugin bug fix update 2015-03-05 15:18:04 UTC

Description Stephen Herr 2013-09-09 21:15:29 UTC 
+++ This bug was initially created as a clone of Bug #1006037 +++

yum-rhn-plugin-1.10.1-1 and higher now accept a timeout parameter from yum instead of implicitly relying on the rhn-client-tools defaults. However, this can lead to less-than-ideal results for some people given that the yum default is 30s and the rhn-client-tools default was 120s.

Let's make yum-rhn-plugin have its own timeout default of 120s. If it is not set then we can fall back to the yum.conf timeout or yum's default if neither are set.

--- Additional comment from Stephen Herr on 2013-09-09 16:32:56 EDT ---

Committing to Spacewalk master:
62b3036b9503d4dbbc9d503275ba06c511c85653
Comment 1 Stephen Herr 2013-09-09 21:16:20 UTC 
We should make sure this gets into RHEL 7 as well.
Comment 8 errata-xmlrpc 2015-03-05 10:52:02 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0473.html
Note You need to log in before you can comment on or make changes to this bug.