Bug 1483137 - subscription-manager has a default timeout of 60 seconds, this needs to be configurable for a heavily utilized Satellite6 environment
Summary: subscription-manager has a default timeout of 60 seconds, this needs to be co...
Keywords:
Status: CLOSED DUPLICATE of bug 1346417
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.2.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-18 20:13 UTC by sthirugn@redhat.com
Modified: 2017-08-18 20:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-18 20:19:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description sthirugn@redhat.com 2017-08-18 20:13:42 UTC
Description of problem:
subscription-manager has a default timeout of 60 seconds, this needs to be configurable for a heavily utilized Satellite6 environment.

Version-Release number of selected component (if applicable):
Satellite 6.2.11

How reproducible:
Always

Steps to Reproduce:
see https://bugzilla.redhat.com/show_bug.cgi?id=1483136 - In a heavily loaded Satellit6 system, registration can take longer than 60 seconds in certain scenarios and this will cause failure of registrations of clients.

Actual results:
Explained above

Expected results:
If subscription-manager doesn't time out in 60 seconds, satellite will eventually finish the registration and handover proper subscriptions to the requesting client

Additional info:

Comment 1 Karl Abbott 2017-08-18 20:18:40 UTC
Appears to be a duplicate of:

https://bugzilla.redhat.com/show_bug.cgi?id=1346417

You can set in the server section of rhsm.conf:

server_timeout=120

and that will cause subscription_manager to wait for 2 minutes or until the work is done, whichever comes first.

We tested it by setting the timeout to 1 second and it immediately exited.

Karl

Comment 2 sthirugn@redhat.com 2017-08-18 20:19:17 UTC

*** This bug has been marked as a duplicate of bug 1346417 ***


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