Bug 1234473

Summary: Repo syncs should always fail completely rather than be paused
Product: Red Hat Satellite Reporter: Justin Sherrill <jsherril>
Component: Content ManagementAssignee: Justin Sherrill <jsherril>
Status: CLOSED CURRENTRELEASE QA Contact: Corey Welton <cwelton>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: bbuckingham, bkearney, cwelton, jsherril, sthirugn
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/10901
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 16:04:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Justin Sherrill 2015-06-22 15:26:01 UTC

Comment 1 Justin Sherrill 2015-06-22 15:26:02 UTC
Created from redmine issue http://projects.theforeman.org/issues/10901

Comment 2 Justin Sherrill 2015-06-22 15:26:04 UTC
Upstream bug assigned to jsherril

Comment 5 Bryan Kearney 2015-07-10 20:26:41 UTC
Delivered with Snap12.

Comment 7 Justin Sherrill 2015-07-13 15:08:02 UTC
This may be difficult to reproduce as it typically only occurs under high load when a task such as the content indexing fails.  

One thing you can try is stopping httpd right after the sync step finishes of the task.  Wait a few minutes and start httpd and examine the task.  This may behave funny since the rails server is also running in httpd, but its the best i can think of without modifying the code to simulate the error.

Comment 10 Corey Welton 2015-07-24 17:16:51 UTC
Verified in SNAP14

Comment 11 Bryan Kearney 2015-08-12 16:04:38 UTC
This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.