Bug 1479515

Summary: [RFE] Improve Satellite Task Management
Product: Red Hat Satellite Reporter: Christian Marineau <cmarinea>
Component: InfrastructureAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Pramuk <lpramuk>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.10CC: aperotti, bkearney, brcoca, cdonnell, jcallaha, kbost, kdixon, mmccune, rdixon, schamilt, shughes, sokeeffe, tasander, vanhoof
Target Milestone: UnspecifiedKeywords: FutureFeature, PrioBumpGSS, PrioBumpPM, UserExperience
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-19 08:35:57 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:
Bug Depends On:    
Bug Blocks: 1385841, 1399395    

Description Christian Marineau 2017-08-08 17:02:08 UTC 
Description of problem:

As a Satellite user, I would need the product to have a better management concerning  tasks.

I would like to:
  -Avoid the accumulation of Pending/Paused Tasks
  -Avoid having to Clean/Destroy/Unlocks Tasks
  -Not having to deal with Dynflow console
  -Have a better notification about the underlying issue (errored/paused  tasks often being a collateral effect)
  -Dynflow should have a skip all link to include resume the task
  -Foreman rake console and dynflow should be locked to only 1 Satellite user session to prevent concurrent task destroying

A lot of issues required involving interaction with Tasks, which is time consuming, can lead to mistakes or data inconsistency.
Comment 1 Rick Dixon 2017-08-08 17:08:04 UTC 
Two asks from me:


1) I'd also like to suggest global option for task handling, depending on the level of task involvement the user wants:

For example:

AUTO
Would NOT allow tasks to settle in a paused state (holding locks) if at all possible; complicated tasks that reach a paused state and require user interaction should be automatically “rolled back” into a stopped state, releasing the lock.

MANUAL
Allows tasks to pause for manual, step-by-step user intervention of individual steps. Locks are held in the meantime.



2) Some kind of console command to force recursively skipping all related steps in a specific task. Preferably, initiating this by task id on a paused/error task would:
 	- resume the task
        - check for settlement into a paused state
        - recursively skip all skippable steps 
        - resume the task 
        - rinse/repeat until the task reaches a stopped state

            # foreman-rake katello:taskcleanup  TASK_UUID --force-skip
Comment 7 Sean O'Keeffe 2019-12-19 08:35:57 UTC 
Over the past 3 years we have made countless improvements to tasks themselves and the management of them, we no longer see such widespread issues with tasks. I'm therefore closing this. If you feel differently, please feel free to open a more targeted RFE for any task improvements we should.