This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 984009 - ssl timeout while adding large number of systems
ssl timeout while adding large number of systems
Product: Subscription Asset Manager
Classification: Red Hat
Component: Splice (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: 1.3
Assigned To: Chris Duryee
Depends On:
Blocks: sam13-tracker
  Show dependency treegraph
Reported: 2013-07-12 09:58 EDT by Vitaly Kuznetsov
Modified: 2013-10-01 07:03 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-01 07:03:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vitaly Kuznetsov 2013-07-12 09:58:14 EDT
Description of problem:
During SST sync with katello ssl timeout can happen:
  File "/usr/bin/spacewalk-splice-checkin", line 93, in <module>
  File "/usr/lib/python2.6/site-packages/spacewalk_splice_tool/", line 188, in main
  File "/usr/lib/python2.6/site-packages/spacewalk_splice_tool/", line 146, in spacewalk_sync
    katello_consumer_list = katello_client.get_consumers(with_details=False)
  File "/usr/lib/python2.6/site-packages/spacewalk_splice_tool/", line 166, in get_consumers
  File "/usr/lib/python2.6/site-packages/katello/client/api/", line 171, in systems_by_org
    return self.server.GET(path, query)[1]
  File "/usr/lib/python2.6/site-packages/katello/client/", line 425, in GET
    return self._request('GET', path, queries, custom_headers=custom_headers)
  File "/usr/lib/python2.6/site-packages/katello/client/", line 249, in _request
    return self._process_response(connection.getresponse())
  File "/usr/lib64/python2.6/", line 990, in getresponse
  File "/usr/lib64/python2.6/", line 391, in begin
    version, status, reason = self._read_status()
  File "/usr/lib64/python2.6/", line 349, in _read_status
    line = self.fp.readline()
  File "/usr/lib64/python2.6/", line 433, in readline
    data = recv(1)
  File "/usr/lib64/python2.6/", line 215, in recv
  File "/usr/lib64/python2.6/", line 136, in read
ssl.SSLError: The read operation timed out

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

How reproducible:
Always for e.g. 300 systems

Steps to Reproduce:
1. Create 300 systems in spacewalk (splice-export report)
2. Run SST
3. Update 300 systems (new checkins,...)
4. Run SST again

Actual results:
Traceback (above)

Expected results:
Sync goes normally

Additional info:
Comment 1 Chris Duryee 2013-07-12 10:10:13 EDT
The proposed fix for this is to call the "systems_by_org" API with pagination, so we don't hit a timeout.
Comment 2 Chris Duryee 2013-07-24 16:17:55 EDT
spacewalk-splice-tool ea56dad16d5 0.35

if you set debug logging on sst, you'll see pagination messages like:

2013-07-24 20:11:10,417 DEBUG spacewalk_splice_tool.katello_connect katello_connect:get_consumers: retrieving systems for org satellite-3, offset 0
2013-07-24 20:11:15,390 DEBUG spacewalk_splice_tool.katello_connect katello_connect:get_consumers: found 25 systems
2013-07-24 20:11:15,391 DEBUG spacewalk_splice_tool.katello_connect katello_connect:get_consumers: retrieving systems for org satellite-3, offset 25
2013-07-24 20:11:19,552 DEBUG spacewalk_splice_tool.katello_connect katello_connect:get_consumers: found 20 systems
Comment 3 Bryan Kearney 2013-08-02 14:51:34 EDT
SNAP0 contains these bug fixes. Moving to ON_QA.
Comment 5 Vitaly Kuznetsov 2013-08-21 10:24:43 EDT
Verified with 300 systems upload,

10 uploads took 4460 seconds (446 sec./upload, 1.5 sec./system)
Comment 7 errata-xmlrpc 2013-10-01 07:03:12 EDT
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.

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