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.
DescriptionChristian 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.
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
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.