Bug #21802
Recurring tasks need to be more resilient
Pull request:
Fixed in Releases:
Found in Releases:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1518576
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a recurring task
2. Cancel the task, while leaving the recurring logic running
Actual results:
The recurring logic stays active forever without actually spawning any more tasks.
Expected results:
The recurring logic either cancels itself or tries to recreate the cancelled task.
Additional info:
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot about 3 years ago
Updated by - Assignee set to Adam Ruzicka
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-tasks/pull/311 added
#2
Updated by Adam Ruzicka about 3 years ago
Updated by - Copied to Bug #22700: Use the facilities from foreman-tasks for more resilient recurring jobs added
#3
Updated by Anonymous almost 3 years ago
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset 6d0d96188a8b74973089436c89aa93e34d40855d.
#4
Updated by Marek Hulán almost 3 years ago
Updated by - Related to Bug #23008: rss notifications: no implicit conversion of Time into String added
#5
Updated by Ivan Necas over 2 years ago
Updated by - Related to Bug #23849: Current user is not set when triggering repetitions of recurring actions added
Fixes #21802 - Make recurring tasks more resilient
Before this fix cancelling a task belonging to a recurring logic would
make the recurring logic be active forever without triggering another
repetition.
Additionally, it also fixes time loading from dynflow after schema normalization.