Bug 1480362

Summary: Scheduling a remote job to recurring creates identical duplicate sub-tasks
Product: Red Hat Satellite Reporter: Satellite Program <pm-sat>
Component: Remote ExecutionAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: urgent    
Version: 6.2.0CC: aruzicka, bbuckingham, bkearney, inecas, itewksbu, jcallaha, mmccune, pondrejk, xdmoon
Target Milestone: UnspecifiedKeywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_remote_execution-1.3.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1478886 Environment:
Last Closed: 2018-02-21 17:06:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1473341    
Bug Blocks:    
Attachments:
Description Flags
tasks none

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