Bug 1238223 - [RFE] subscription expiration reminder: Indicate to the user within a time interval that Subscription Manifest are going to expire
Summary: [RFE] subscription expiration reminder: Indicate to the user within a time in...
Keywords:
Status: CLOSED DUPLICATE of bug 1410616
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Tom McKay
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-01 12:29 UTC by Roy Williams
Modified: 2022-03-13 13:57 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-05 15:37:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10966 0 Normal Rejected Indicate to the user within a time interval that Subscription Manifest are going to expire 2020-12-23 14:53:58 UTC
Red Hat Issue Tracker SAT-6869 0 None None None 2021-12-10 14:46:42 UTC

Description Roy Williams 2015-07-01 12:29:20 UTC
Description of problem:
Subscription manifest should provide notification to the user in Satellite 6 to indicate a manifest expiration is coming, up to a month before it actually occurs. 

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

When subscription manifest expire there is no indication that has happened through out the interface.

Comment 1 RHEL Program Management 2015-07-01 12:45:28 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Devan Goodwin 2015-08-13 12:35:53 UTC
Moving to Satellite web UI. 

For clarity the manifest won't expire, but some subscriptions within it might. Data on subscriptions and their expiration is available in candlepin API, Satellite would just need to figure out when to check and how to display it.

If you'd like any API enhancements to do so just let us know.

Comment 5 Bryan Kearney 2015-12-10 16:46:41 UTC
There is dashboard element called "Current Subscription Totals" which shows the current susbcriptions, those that expire in 120 days, and recently expireed. Is that not acceptable?

Comment 9 Bryan Kearney 2016-04-27 19:11:32 UTC
Upstream bug assigned to tomckay

Comment 10 Bryan Kearney 2016-04-27 19:11:34 UTC
Upstream bug component is Candlepin

Comment 11 Bryan Kearney 2016-12-05 21:01:28 UTC
Upstream bug assigned to tomckay

Comment 12 Bryan Kearney 2016-12-05 21:01:32 UTC
Upstream bug component is Candlepin

Comment 17 Roy Williams 2018-03-01 18:35:43 UTC
(In reply to Bryan Kearney from comment #5)
> There is dashboard element called "Current Subscription Totals" which shows
> the current susbcriptions, those that expire in 120 days, and recently
> expireed. Is that not acceptable?

I apologize for the lack of response, I no longer work for the university where I was using this. Anyway the issue was the subscription expired in Satellite 6 and we had no way of knowing that had happened, until the hosts all lost their subscriptions. Although I imagine a lot has been fixed by now, at the time the connected hosts lost their entitlements as expected. Although we didn't get any kind of notification from Satellite 6 that this was about to happen. I did attempt to modify the entitlements with new ones, but that didn't resolve the machines that had totally lost their entitlements to the repositories. 

I was forced to reinstall the katello consumer for the machines that were using Satellite 6 to get their updates to resolve it. 

I initially thought it was the manifest itself expiring, but from RHN, the place I retrieved the manifest, it seemed to appear that the entitlements associated with the manifest would expire. That's the way it appeared to me.

Comment 18 Bryan Kearney 2018-07-05 15:37:26 UTC

*** This bug has been marked as a duplicate of bug 1410616 ***


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