+++ This bug was initially created as a clone of Bug #2222968 +++

Problem Description:

Many Satellite customers using old versions are giving feedback that they were not aware that the version of satellite they are using is EOL so they did not plan to upgrade it to the supported version.

This leads to many customers reporting support cases for EOL versions and we need to process support exceptions for the customer till they plan the upgrade.

We would like to have a warning banner message on the satellite webui which is easily visible for the customers. ( Login page or on the Dashboard page)

We can point customers to use a Satellite upgrade helper for upgrading their satellite server.

— Additional comment from on 2023-07-17T12:24:33Z

What are the expectations here? Should Satellite check somewhere whether a new version is out and then show this? Or should we bake in the expected next release date and show this once the date gets passes?

— Additional comment from on 2023-07-17T16:09:12Z

I did not propose any possible solutions here but these are the thoughts I have currently:

• Satellite lifecycle page ( https://access.redhat.com/support/policy/updates/satellite ) provide API, which we can call from Satellite to get an update about the product version moving from Full support to Maintenance to EOL
• We can use, an RSS feed to push a message to connected satellite servers where we will have a tool on satellite that will read the EOL message coming from the RSS feed, enable and display a warning banner on the satellite webui.
• We can build and provide a package (every 6 months) that will have metadata about supported and maintenance version, where it will have a script that will detect the installed satellite version and accordingly it will add the warning banner on Webui. This package can be part of "Red Hat Satellite Client 6" ( version independent repo) so with less efforts we can reach to all satellite customers.

— Additional comment from on 2023-07-19T14:59:31Z

Customer update from case no: 03564287
===========
Hi Sneha,
We just came to know that our satellite version is EOL and we have to update the satellite to the new version 6.11 or 6.13.
But at this moment we are in the middle of the OpenStack Cisco ACI Plugin upgrade activity. All compute and controller nodes are registered with the satellite but only two nodes are (psvccmptovs02, Director node) not getting registered. For this reason, we are not getting able to complete the OSP upgrade process.

So we need support exception of the satellite server so that we can complete the OSP Cisco plugin upgrade process and after that, we can work on the satellite server upgrade.
Thanks for understanding.
===========

— Additional comment from on 2023-09-14T08:12:25Z

Customer update from case no: 03613044

=========
Hello Anand,

I confirm reviewing the KB article located at https://access.redhat.com/solutions/1421903 and that subscription manager release was already set for the host. We're requesting Red Hat to raise a support exception for us.

1. We didn't realize v6.10 was EOL and that were so far back that were unable to be provided support.
2. We will upgrade Satellite as soon as we can. We have a fairly aggressive patch schedule so we will have to find a window of opportunity to start the upgrade.
3. The only blocker for Satellite upgrade is time. Our aggressive patch schedule will make it a challenge.

Since this case doesn't qualify for Sev-2 support we have reduced it down to Sev-3 (Normal).

=========

— Additional comment from on 2023-10-30T11:29:29Z

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

— Additional comment from on 2023-11-27T15:23:56Z

Verified in Stream snap 38