Bug 973775 - One system can get at 'Default' and 'Inactive' reports at the same time
Summary: One system can get at 'Default' and 'Inactive' reports at the same time
Alias: None
Product: Subscription Asset Manager
Classification: Red Hat
Component: Splice (Show other bugs)
(Show other bugs)
Version: 1.3
Hardware: Unspecified Unspecified
Target Milestone: rc
: ---
Assignee: wes hayutin
QA Contact: mkovacik
Depends On:
Blocks: sam13-tracker
TreeView+ depends on / blocked
Reported: 2013-06-12 17:28 UTC by Vitaly Kuznetsov
Modified: 2013-10-01 10:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-01 10:56:26 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1390 normal SHIPPED_LIVE Release 1.3 of Subscription Asset Manager 2013-10-01 14:43:14 UTC

Description Vitaly Kuznetsov 2013-06-12 17:28:03 UTC
Description of problem:
Sometimes a system gets into 'Default' and 'Inactive' report at the same time with different checkin dates. 

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

How reproducible:

Steps to Reproduce:
1. Create checkins for a particular system for a month (every 4 hours)
2. Create Default and Inactive reports

Actual results:
System is reported twice

Expected results:
System should be reported as Active only

Additional info:
This issue can be mitigated by creating consolidated report with all Active/Inactive/Deleted systems included (GA plans).

Comment 1 wes hayutin 2013-06-18 13:25:01 UTC

I believe this is fixed in the above commit. 
Moving to on_qa

Comment 3 Vitaly Kuznetsov 2013-06-21 15:25:37 UTC
Verified in ruby193-rubygem-splice_reports-0.0.5-27.el6sam.noarch

Comment 6 errata-xmlrpc 2013-10-01 10:56:26 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.


Note You need to log in before you can comment on or make changes to this bug.