Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.

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:

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

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