Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1518576

Summary: Recurring tasks need to be more resilient
Product: Red Hat Satellite 6 Reporter: Adam Ruzicka <aruzicka>
Component: Tasks PluginAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Jan Hutaƙ <jhutar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: aruzicka, bbuckingham, inecas, jhutar
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:28:47 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:

Description Adam Ruzicka 2017-11-29 08:44:25 UTC
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:

Comment 1 Adam Ruzicka 2017-11-29 08:51:49 UTC
Created redmine issue from this bug

Comment 3 2018-01-17 11:27:13 UTC
Upstream bug assigned to

Comment 4 2018-01-17 11:27:16 UTC
Upstream bug assigned to

Comment 5 2018-03-27 22:27:02 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue has been resolved.

Comment 7 Bryan Kearney 2018-10-16 19:28:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.