Bug 1218378

Summary:	Unable to resume stopped repo sync
Product:	Red Hat Satellite	Reporter:	Brad Buckingham <bbuckingham>
Component:	Repositories	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	akarlsso, inecas, mjs, sauchter, sthirugn, xdmoon
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-26 13:27:55 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 Brad Buckingham 2015-05-04 18:21:09 UTC

Description of problem:

Unable to resume stopped repo sync task.  If reposync is failed due to any reason (eg network) the task goes in stopped state, we tried resuming the task but the sync was not started again. 

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

How reproducible:
Always

Additional info:
This issue was raised by AshishH during a Beta test day.

Comment 2 Stuart Auchterlonie 2015-05-18 13:48:34 UTC

I've hit this on 6.0, and my customer has hit this in 6.1 beta.

I triggered this by running out of disk space, my customer triggered
it by rebooting the server while the sync tasks were in progress

I did identify a workaround, however it is extremely cumbersome
to action.

- Go to the tasks list and identify the tasks that are paused / errored

- for each <task>
  - if there is another task listed as blocking it, goto that task
  - if there is no task blocking it, go to the dynflow console,
    and identify which sub task still thinks it is running.
  - skip this sub task
  - go back and resume the task
  - task should now complete.

Rinse and repeat for *every* task.

Comment 4 Ivan Necas 2016-04-26 13:27:55 UTC

Seems like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1317986 that got fixed and will be part of 6.2. I was not able to reproduce the issue with the latest 6.2 snap. Please reopen if there is an indication that this behavior appears again in 6.2

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