Bug 977314

Summary: system is not present in both Active and Inactive reports
Product: [Retired] Subscription Asset Manager Reporter: Vitaly Kuznetsov <vkuznets>
Component: SpliceAssignee: Splice Developers <splice-devel>
Status: CLOSED ERRATA QA Contact: mkovacik
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.3CC: bkearney, cduryee, jmatthew, whayutin
Target Milestone: rc   
Target Release: 1.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-01 10:58:44 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 833466    

Description Vitaly Kuznetsov 2013-06-24 09:59:59 UTC 
Description of problem:
System can be absent in both Active and Inactive reports when creating report for inactivity period in the past.

Version-Release number of selected component (if applicable):
ruby193-rubygem-splice_reports-0.0.5-27.el6sam

How reproducible:
always

Steps to Reproduce:
1. Create regular checkins for a week (invalid state, 42 checkins)
2. Do not do any checkins for a week
3. Create regular checkins for a week (valid state, 42 checkins)
4. Try creating Active/Inactive reports for 'gap period' (second week).

Actual results:
The system won't show up in both Active and Inactive reports

Expected results:
The system is reported in Inactive report

Additional info:
Comment 1 wes hayutin 2013-06-24 16:47:32 UTC 
fixed in:
commit b85b27fbb3e097fe107cc2581c28661efe3b1eb8

* [new tag]         rubygem-splice_reports-0.0.5-28-sat -> rubygem-splice_reports-0.0.5-28-sat
Comment 3 Bryan Kearney 2013-08-02 18:52:30 UTC 
SNAP0 contains these bug fixes. Moving to ON_QA.
Comment 5 Vitaly Kuznetsov 2013-08-21 13:31:47 UTC 
Verified with ruby193-rubygem-splice_reports-0.0.5-40.el6sam
Comment 7 errata-xmlrpc 2013-10-01 10:58:44 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.

http://rhn.redhat.com/errata/RHEA-2013-1390.html