Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

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.

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.

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 ***