Bug 1360330

Summary: Scheduled reports are emailing ever few seconds rather then just 1
Product: Red Hat CloudForms Management Engine Reporter: John Prause <jprause>
Component: ReportingAssignee: Joe Rafaniello <jrafanie>
Status: CLOSED ERRATA QA Contact: Jiri Stefanisin <jistefan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.5.0CC: cpelland, dajohnso, jhardy, jistefan, jrafanie, obarenbo
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 5.6.1.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1354629 Environment:
Last Closed: 2016-08-18 17:59:58 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: 1354629    
Bug Blocks:    

Comment 2 Joe Rafaniello 2016-08-01 14:12:43 UTC 
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/85c117362f898d357d7a02377e9f82f4a17f3a61

commit 85c117362f898d357d7a02377e9f82f4a17f3a61
Author:     d-m-u <duhlmann>
AuthorDate: Thu Jul 28 17:29:19 2016 -0400
Commit:     d-m-u <duhlmann>
CommitDate: Thu Jul 28 17:29:19 2016 -0400

    Avoid issue with Rufus caching time within options
    
    Rufus scheduler 3.0.8+ started modifying the input options hash at
    jmettraux/rufus-scheduler@c074a59
    
    This commit allows schedules to parse the time using Chronic.
    Unfortunately, for speed, they cache the result of the first parse in the
    input options hash, causing us to schedule the same time many times!
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1360332

 app/models/miq_schedule_worker/runner.rb       | 4 ++--
 spec/models/miq_schedule_worker/runner_spec.rb | 3 +++
 2 files changed, 5 insertions(+), 2 deletions(-)
Comment 6 errata-xmlrpc 2016-08-18 17:59:58 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://rhn.redhat.com/errata/RHSA-2016-1634.html