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.
Bug 1480362 - Scheduling a remote job to recurring creates identical duplicate sub-tasks
Summary: Scheduling a remote job to recurring creates identical duplicate sub-tasks
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: Unspecified
Assignee: Adam Ruzicka
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On: 1473341
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-10 19:51 UTC by Satellite Program
Modified: 2020-12-14 09:28 UTC (History)
9 users (show)

Fixed In Version: tfm-rubygem-foreman_remote_execution-1.3.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1478886
Environment:
Last Closed: 2018-02-21 17:06:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
tasks (9.40 KB, image/png)
2017-10-16 15:37 UTC, Peter Ondrejka 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20107 0 None None None 2017-08-10 19:51:14 UTC

Comment 2 Peter Ondrejka 2017-10-16 15:30:14 UTC 
Tested on satellite-6.3.0-20.0.beta.el7sat.noarch, the future-scheduled job is not executed at all, it remains in the queued state, see attachment
Comment 3 Peter Ondrejka 2017-10-16 15:37:02 UTC 
Created attachment 1339317 [details]
tasks
Comment 4 Satellite Program 2017-10-16 16:06:58 UTC 
Upstream bug assigned to aruzicka
Comment 5 Ivan Necas 2017-10-17 07:57:10 UTC 
@peter: I was not able to reproduce this issue with the latest snap. Could you give it a try on different sat instance?

Also, could you have a look at https://sat63-qa-rhel7.example.com/foreman_tasks/dynflow/worlds and use 'check status` link to see, what's the dynflow's status?
Comment 6 Peter Ondrejka 2017-10-19 09:20:40 UTC 
hm ok, can't reproduce it either, it might have had a load on the satellite that kept those tasks queued, nevermind
Comment 7 Bryan Kearney 2018-02-21 17:06:36 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.

https://access.redhat.com/errata/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.