Bug 1173133

Summary: Red Hat repos sync stuck forever at 68 or 69%
Product: Red Hat Satellite Reporter: Pavel Moravec <pmoravec>
Component: Content ManagementAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.6CC: mmccune, nerawat
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-19 16:41:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pavel Moravec 2014-12-11 13:47:43 UTC
Description of problem:
When synchronizing some Red Hat repositories, the relevant tasks are stuck at either 68% or 69%.

Attached is foreman-debug with debugs enabled.


Version-Release number of selected component (if applicable):
pulp-server-2.4.3-1.el6sat.noarch
katello-1.5.0-30.el6sat.noarch


How reproducible:
n.a.


Steps to Reproduce:
???


Actual results:
sync tasks stuck


Expected results:
sync tasks finish at some (reasonable) time


Additional info:
production.log contains several interesting info:
1) "PulpExecutionException: Importer indicated a failed response" is raised twice
2) Some tasks are changing their status between running and suspended in endless loop, like:

         Step 736706b6-55ca-4af9-a6bb-af6ef9a2e04d: 3   running >> suspended in phase      Run Actions::Pulp::Repository::Sync
         Step 736706b6-55ca-4af9-a6bb-af6ef9a2e04d: 3 got event Dynflow::Action::Polling::Poll
         Step 736706b6-55ca-4af9-a6bb-af6ef9a2e04d: 3 suspended >>   running in phase      Run Actions::Pulp::Repository::Sync
         Step 736706b6-55ca-4af9-a6bb-af6ef9a2e04d: 3   running >> suspended in phase      Run Actions::Pulp::Repository::Sync

Comment 4 Mike McCune 2014-12-19 16:41:56 UTC
This looks like a duplicate of 1176157 which we are going to resolve in a 6.0.X ZStream release as soon as possible.

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