Bug #9237
closedPublish content view version failing on several dynflow tasks
Description
Use case:
- create several repositories
- start syncing them
- sync paused due to disk space issues.
- after adding disk space, sync jobs restarted
- meanwhile created new version of a content view containing the repos above
- Publish content view task fails: cannot cancel parent tasks in GUI (browser timeouts)
- Dynaflow view shows a lot of tasks paused or in error. Have to skip/cancel one at the time, reload, resume workflow.
Is there a way of cancelling/removing entire workflow? Like a clean up procedure?
Updated by Ivan Necas about 9 years ago
- Tracker changed from Support to Bug
- Project changed from foreman-tasks to Katello
- Triaged set to No
Moving to Katello project, as the issue is not in the realm of the foreman-tasks itself.
As per the canclelling the whole workflow, it's not good idea in general (as the
tasks not being performed were there for a reason, so their skipping
might lead to more serious /and unpredicable/ issues later: it's just postponing
the issue). One can do 'Force stop' and the task which unlocks the touched resources
so that other tasks can run against it without the lock issue
Updated by Eric Helms about 9 years ago
- Category set to Orchestration
- translation missing: en.field_release set to 23
- Triaged changed from No to Yes
Updated by Eric Helms about 9 years ago
- translation missing: en.field_release changed from 23 to 31
Updated by Eric Helms about 9 years ago
- translation missing: en.field_release deleted (
31)
Updated by Eric Helms over 8 years ago
- translation missing: en.field_release set to 86
Updated by Eric Helms about 8 years ago
- translation missing: en.field_release changed from 86 to 114
Updated by John Mitsch over 4 years ago
- Status changed from New to Rejected
- Target version deleted (
Katello Backlog)
Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.