Bug 2075163

Summary:	[RFE] Notification when manifest is going to expire
Product:	Red Hat Satellite	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Subscription Management	Assignee:	Jeremy Lenz <jlenz>
Status:	CLOSED MIGRATED	QA Contact:	visawant
Severity:	high	Docs Contact:
Priority:	high
Version:	6.10.0	CC:	aganbat, ahumbe, bbuckingham, chrobert, crog, dsinglet, jbhatia, jentrena, jlenz, lufu, mkalyat, momran, parmstro, pdwyer, rjerrido, rlavi, sadas, saydas, sriley, swachira, tasander, thadzhie, visawant, zhunting
Target Milestone:	stream	Keywords:	FutureFeature, MigratedToJIRA, PrioBumpGSS
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 12:21:03 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:

Description Waldirio M Pinheiro 2022-04-13 18:19:18 UTC

Description of problem:
Adding the notification feature to keep the customer aware once the manifest is going to expire or got expired, will help to prevent some issues that we got via side effects on console.redhat.com.

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


How reproducible:
100%

Steps to Reproduce:

1. The manifest itself got expired
2. After some time, console.redhat.com will not be receiving the satellite data and the servers will get removed as old entries
3. 

Actual results:
* The customer didn't get any notification about that and hence it's an unpredictable situation for them.
* Satellite is unable to sync any repos ( 403 forbidden )
* Patching on client system fails , as the satellite is using on_demand content and fails to download the same with same 403 forbidden error.

Expected results:

* The customer be notified that the manifest got expired, in this way, they can work to get a new one and refresh on Satellite, avoiding issues on console.redhat.com or with any operations that involve connecting with Red Hat CDN
* More information is provided within the internal comments of this BZ.


Additional info:

AAP provides a feature where the user can connect to the Red Hat portal itself and create a manifest with Ansible-specific subscriptions and import it. Perhaps the same idea can be applied here for the update of the expiry of Manifest IdCert as well someway

Comment 3 Waldirio M Pinheiro 2022-04-13 19:06:38 UTC

Hello

I can see that on Satellite 6.10 we have already this feature.

Administer - Users - <click over the user> - "Email Preferences" tab - "Subscriptions expiring soon" with some additional options

 - No emails / Daily / Weekly / Monthly

And also it's possible to set the # of days to start matching

 - 120 - System default / 7 / 30 / 60 / 90 / 120 / 180



@saydas is there anything else that you believe that could be added? If not, I believe we can archive this one.

Thank you!
Waldirio

Comment 4 Sayan Das 2022-04-13 19:25:37 UTC

(In reply to Waldirio M Pinheiro from comment #3)
> Hello
> 
> I can see that on Satellite 6.10 we have already this feature.
> 
> Administer - Users - <click over the user> - "Email Preferences" tab -
> "Subscriptions expiring soon" with some additional options
> 
>  - No emails / Daily / Weekly / Monthly
> 
> And also it's possible to set the # of days to start matching
> 
>  - 120 - System default / 7 / 30 / 60 / 90 / 120 / 180
> 
> 
> 
> @saydas is there anything else that you believe that could be
> added? If not, I believe we can archive this one.
> 
> Thank you!
> Waldirio


I could be very very wrong but We have two scheduled jobs:

SendExpireSoonNotifications --> Which checks the expiry of subscriptions and that is related to the email ""Subscriptions expiring soon" [ https://access.redhat.com/solutions/6099481 ]

CreateExpiredManifestNotifications --> Which checks the expiry of the subscription manifest itself and only reports in Content --> Subscriptions page when the zip is expired. But I don't see any Email preference for this one.


If there is one, I perhaps missed seeing it for sure but do let me know if you find that option.



-- Sayan

Comment 16 Jeremy Lenz 2023-08-28 18:49:29 UTC

*** Bug 2233587 has been marked as a duplicate of this bug. ***

Comment 17 Dana Singleterry 2023-09-20 10:05:42 UTC

*** Bug 2223428 has been marked as a duplicate of this bug. ***

Comment 18 Brad Buckingham 2023-10-30 11:29:29 UTC

Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Comment 22 Paul Armstrong 2024-04-24 20:03:12 UTC

https://access.redhat.com/solutions/11101

"The only action that could extend the expiry date of this certificate for an already imported manifest is replacing that certificate, which is done when you import a new zip of the same old manifest."

This is not a true statement. I have followed the procedure running Satellite 6.15: 1) Run the rake task: sudo foreman-rake console << EORAKE org = Organization.find(1) File.write('/tmp/cert_upstream.pem', org.owner_details['upstreamConsumer']['idCert']['cert']) EORAKE 2) run the following to get the date of the certificate rct cat-cert /tmp/cert_upstream.pem | grep -i Date Start Date: 2023-12-10 04:20:05+00:00 End Date: 2024-12-10 05:20:05+00:00 3) Login to the portal, select the manifest and add new subscriptions (so I see changes) 4) Download and import the new manifest zip file. Completes with success. I see the new subs. 5) Run the rake task: sudo foreman-rake console << EORAKE org = Organization.find(1) File.write('/tmp/cert_upstream.pem', org.owner_details['upstreamConsumer']['idCert']['cert']) EORAKE 6) run the following to get the date. The date remains unchanged. rct cat-cert /tmp/cert_upstream.pem | grep -i Date Start Date: 2023-12-10 04:20:05+00:00 End Date: 2024-12-10 05:20:05+00:00

There seems to be another trigger for when the manifest's distributor certificate expires. It would be nice to understand what is really going on and when.

Comment 26 Eric Helms 2024-06-06 12:21:03 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.