Actions
Bug #19570
closedtasks that hit lock error remain in 'pending'
Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman plugin
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Description
When performing some action that takes a lock, if another task is holding that lock the task correctly errors. For some reason though, the task is left in 'planning' state. See screenshot for an example.
I'm not sure when this started, but it first started being reported with katello 3.4 (foreman-tasks-0.9.1-1)
Files
Updated by The Foreman Bot almost 8 years ago
- Status changed from New to Ready For Testing
- Assignee set to Adam Ruzicka
- Pull request https://github.com/theforeman/foreman-tasks/pull/249 added
Updated by Adam Ruzicka almost 8 years ago
- Category set to Foreman plugin
- Target version set to 1.13.1
Updated by Adam Ruzicka almost 8 years ago
- Related to Bug #18963: use the new batch processing feature for bulk tasks added
Updated by Adam Ruzicka almost 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset b58b2e691af724436cf1d351d255c0ec9a6c887d.
Updated by Ivan Necas almost 8 years ago
- Translation missing: en.field_release set to 252
Actions