Bug 2218983 - clicking 'Cancel' in the UI for a Sync task only cancels one sub-task and leaves a stuck sync without progress
Summary: clicking 'Cancel' in the UI for a Sync task only cancels one sub-task and lea...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Tasks Plugin
Version: 6.12.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-30 19:04 UTC by Vincent S. Cojot
Modified: 2023-07-04 00:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Vincent S. Cojot 2023-06-30 19:04:56 UTC
Description of problem:

Following the cancellation of an 'import' task, a Capsule sync task got released (it had been pending). When I realized what had happened (the sync task was still at 0% progress), I clicked 'Cancel' in the UI.

12 hours later, the Capsule Sync task was at 12%, showing a single 'Task canceled' and stuck at 12% for several hours. I had to go into the dnyflow console of the stuck Capsule sync task, 'cancel' a sub-task which had been in state waiting and the overall Capsule sync resumed and reached 14%.

I think cliking 'cancel' in the UI for a capsule sync task should cancel all of the sub-tasks and not leave a huge 'complete sync' stuck for hours.

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

[root@w0617ialabrhsat01 foreman]# rpm -qa satellite\*
satellite-installer-6.12.0.5-1.el8sat.noarch
satellite-maintain-0.0.1-1.el8sat.noarch
satellite-cli-6.12.4-1.el8sat.noarch
satellite-common-6.12.4-1.el8sat.noarch
satellite-6.12.4-1.el8sat.noarch


Steps to Reproduce:
1. start a complete sync to a capsule
2. click cancel in the UI for the above task
3. watch what happens


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