Bug 999027 - system disappears from past 'Inactive' reports once it is removed
Summary: system disappears from past 'Inactive' reports once it is removed
Alias: None
Product: Subscription Asset Manager
Classification: Red Hat
Component: Splice   
(Show other bugs)
Version: 1.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Chris Duryee
QA Contact: mkovacik
Depends On:
Blocks: sam13-tracker
TreeView+ depends on / blocked
Reported: 2013-08-20 14:37 UTC by Vitaly Kuznetsov
Modified: 2013-10-01 11:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-10-01 11:20:52 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-08-20 14:37:23 UTC
Description of problem:
System will disappear from past 'Inactive' reports once it is removed, e.g. I have the following data sequence:

1 system:
  checkins [Aug, 16 11:31 - Aug, 18 07:31]
  got removed on Aug 20 07:34

Now if I create report for all states [Active, Inactive, Deleted] for
the following date range [Aug, 19 - Aug, 20] I get it empty (but I
expect 1 system in Inactive state).

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

How reproducible:

Steps to Reproduce:
1. Create system with inactivity period and removal event after it
2. Create report for inactivity period

Actual results:
System doesn't get into report

Expected results:
System gets into report

Additional info:
We have the following rule for Inactive reporting:
 is_deleted = @@c.find({"instance_identifier" => item["identifier"], "deleted" => true})

once system is 'deleted' it won't show up in all 'Inactive' reports (even before removal data). I'd suggest we change this with a rule which says 'delete event before end_date exists'

Comment 1 Chris Duryee 2013-08-20 14:57:23 UTC
ea7be96364a splice-reports 0.0.5-42

thanks for the detailed report with suggested fix:)

Comment 3 Vitaly Kuznetsov 2013-08-23 14:22:27 UTC
Verified with ruby193-rubygem-splice_reports-0.0.7-1.el6sam

Comment 5 errata-xmlrpc 2013-10-01 11:20:52 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.