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 1343160 - Subscription-manager commands sporadically hang, requiring rhsmcertd to be restarted
Summary: Subscription-manager commands sporadically hang, requiring rhsmcertd to be re...
Keywords:
Status: CLOSED DUPLICATE of bug 1346417
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-06 16:23 UTC by Rich Jerrido
Modified: 2019-12-16 05:53 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-11 18:25:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Rich Jerrido 2016-06-06 16:23:40 UTC
Description of problem:
Occasionally subscription-manager commands hang, and the only way to enable a successful run of subscription-manager is to restart the rhsmcertd

Version-Release number of selected component (if applicable):
subscription-manager-1.15.9-15.el7.x86_64

How reproducible:
~50%

Steps to Reproduce:
In my instance, the following steps caused the issue. 
1. install satellite 6's consumer RPM
2. run subscription-manager register. 
3.

Actual results:

the 'subscription-manager register' command hangs. 


Expected results:

subscription-manager commands complete without hanging. 

Additional info:

There are other, non Satellite 6 related instances where this happens, as shown below:

https://access.redhat.com/solutions/2202931
https://access.redhat.com/solutions/2110281
https://access.redhat.com/solutions/1754373
https://access.redhat.com/solutions/1342823

This leads me to believe the issue is not Satellite 6 specific.

Comment 4 Evgeni Golov 2016-06-06 20:08:28 UTC
I've also hit this a couple of times when subscribing RHEL6 (6.3-6.5, with rhsm/sub-man bits from 6.7) guests to Satellite 6.1.

Comment 7 Chris Snyder 2016-06-10 19:02:03 UTC
The PR below should fix this issue, in short, by providing a default timeout to all SSL connections.

PR: https://github.com/candlepin/python-rhsm/pull/170

Comment 8 Alex Wood 2016-06-15 14:29:53 UTC
Hopefully the addition of a socket timeout (3 minutes by default, but configurable via the server_timeout variable) will address this issue, but it's difficult to say given the lack of specifics in the bug report.

Comment 15 Barnaby Court 2017-01-11 18:25:41 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.