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.

Description of problem:  When scheduling a job with future execution, two sub-tasks are being created.  Depending on the type of job, this can cause failures.


Version-Release number of selected component (if applicable): 6.2.10


How reproducible:  Can reproduce everytime via the UI or the API.


Steps to Reproduce:
1.  Run job with future execution.
2.  Upon completion, 2 sub-tasks are listed for the same command.
3.

Actual results:  Job is being executed twice.


Expected results:  Job should only be executed once.


Additional info:  Tested this in an environment with 6.2.9 and the problem doesn't exist.

Still pulling the requested logs, etc. but this may be a duplicate of bug 1473341 depending on the minor revision.

hotfix-1478886 has corrected this issue.

*** Bug 1491938 has been marked as a duplicate of this bug. ***