Bug 1218378 - Unable to resume stopped repo sync
Summary: Unable to resume stopped repo sync
Keywords:
Status: CLOSED DUPLICATE of bug 1317986
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-04 18:21 UTC by Brad Buckingham
Modified: 2020-02-14 17:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-26 13:27:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1458563 0 None None None Never

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


Note You need to log in before you can comment on or make changes to this bug.