Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1593428

Summary: [5.8] Notification in the Satellite UI of EOL
Product: Red Hat Satellite 5 Reporter: Grant Gainey <ggainey>
Component: WebUIAssignee: Grant Gainey <ggainey>
Status: CLOSED ERRATA QA Contact: Radovan Drazny <rdrazny>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 580CC: rdrazny, tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-java-2.5.14-121-sat Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-16 13:16:30 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:
Attachments:
Description Flags
EOL banner on the login page none

Description Grant Gainey 2018-06-20 19:22:58 UTC 
With the impending EOL/ELS of Satellite 5 (https://access.redhat.com/support/policy/updates/satellite), this RFE requests a notification in the Satellite UI similar to that given for an expired certificate to inform the user:

* the date of EOL for their version of Satellite 5
* that without ELS the Satellite will not sync content.
Comment 5 Radovan Drazny 2018-07-12 11:23:13 UTC 
Created attachment 1458349 [details]
EOL banner on the login page

Verified on spacewalk-java-2.5.14-121. As of today (2018-07-12), the banner is not displayed. After modifying the java.eolWarningLead option in the rhn_java.conf to trigger the warning 1000 days before the EOL date (as the default setting of 365 days will display the banner only after 2019-05-31), the banner shows up.
Banner is displayed both on the initial login and on the logout, with the complete information. See the attached image. Links are pointing to correct pages on the customer portal.

VERIFIED
Comment 7 errata-xmlrpc 2018-07-16 13:16:30 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.

https://access.redhat.com/errata/RHEA-2018:2194