Bug 999027
| Summary: | system disappears from past 'Inactive' reports once it is removed | ||
|---|---|---|---|
| Product: | [Retired] Subscription Asset Manager | Reporter: | Vitaly Kuznetsov <vkuznets> |
| Component: | Splice | Assignee: | Chris Duryee <cduryee> |
| Status: | CLOSED ERRATA | QA Contact: | mkovacik |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.3 | CC: | bkearney, cduryee |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-01 11:20:52 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 | ||
ea7be96364a splice-reports 0.0.5-42 thanks for the detailed report with suggested fix:) Verified with ruby193-rubygem-splice_reports-0.0.7-1.el6sam 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 |
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): ruby193-rubygem-splice_reports-0.0.5-40.el6sam How reproducible: always 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'