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.
Bug 1188253 - Capsule sync timeouts everytime
Summary: Capsule sync timeouts everytime
Keywords:
Status: CLOSED DUPLICATE of bug 1169416
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.0.6
Hardware: All
OS: Linux
medium
high
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-02 12:36 UTC by Pavel Moravec
Modified: 2019-03-22 07:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-27 15:24:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Pavel Moravec 2015-02-02 12:36:11 UTC 
Description of problem:
(External) capsule sync everytime "timeouts" (hammer request timeouts, sync itself finishes properly but after a huge time). This happens even if there is nothing new to sync to the capsule.

The duration of capsule sync is approx. 500-1000 seconds everytime.

Task details show "Actions::Pulp::Consumer::SyncNode" task is suspended most of the time (was running for few seconds only). Everytime poll_attempts is many tens (is that an indicator of something bad related to the length of task suspend?)

Network throughput between the capsule and the satellite is fine, scp 100MB file is done within 4seconds.


Version-Release number of selected component (if applicable):
katello-agent-1.5.3-7.el6sat.noarch


How reproducible:
100% at customer side
0% internally (unable to reproduce)


Steps to Reproduce:
n.a.


Actual results:
External capsule sync taking too much time even when no content is really synced. Relevant hammer command timeouts.


Expected results:
Capsule sync to finish sooner, no hammer timeout.


Additional info:
attaching: sosreports, task-export
Comment 4 Mike McCune 2015-02-06 16:40:07 UTC 
This is probably:

https://bugzilla.redhat.com/show_bug.cgi?id=1169416
Comment 5 Brad Buckingham 2015-02-27 15:24:28 UTC 

*** This bug has been marked as a duplicate of bug 1169416 ***
Note You need to log in before you can comment on or make changes to this bug.