Bug 767619

Summary:	Date range for installed products needs to be smarter.
Product:	[Community] Candlepin	Reporter:	William Poteat <wpoteat>
Component:	candlepin	Assignee:	Bryan Kearney <bkearney>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Eric Sammons <esammons>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	0.5	CC:	jsefler, mkhusid
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-17 13:03:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	738066

Description William Poteat 2011-12-14 14:18:20 UTC

The date range for the installed products is far simpler than is needed to truly capture the dates that the client is compliant for a specific product.

The current algorithm gathers the entitlements that have the specific product. Then it reports the first start date and last end date it finds.

This ignores several issues:

Gaps between the first start date and last end date where there is no coverage at all.

Multi-entitlement scenarios where there are entitlements that only partially cover the product during a date range but fully covers it during another date range.

Stacking scenarios where a product can be covered by a stacked product entitlement during a certain period but the actual product during others.



In addition, we need it to be smart enough not to have to iterate through days until it finds what the proper range would be. Right now we do this for the consumer as a whole which is very expensive.

Comment 2 John Sefler 2012-02-27 13:46:22 UTC

Following are two general statements that describe expected results for the new installed product date logic for the cases when the installed product is "GREEN" and "Not GREEN".

Case 1: "GREEN"
When an Installed Product is fully "Subscribed", the start/end dates rendered will overlap today and represent a continuous time period whereby the product remains fully "Subscribed". At no time instance during the Installed Product's date range is the installed product anything but fully "Subscribed".


Case 2: "Not GREEN"
The start/end dates rendered for an Installed Product are "None"(in the CLI)/<blank>(in the GUI) when the status of the installed product is NOT fully "Subscribed" today.  This case implies that the installed product is not compliant today.

Comment 3 Bryan Kearney 2012-07-17 13:03:22 UTC

Marking all community bugs modified or beyong as closed.