End of Life Data for Red Hat Enterprise Linux


Introduction

The standalone Red Hat Enterprise Linux Support Details pattern can provide End of Life data for both Red Hat Enterprise Linux and Red Hat Enterprise Linux CoreOS.

Trigger

This pattern triggers off an OS type of 'Red Hat Enterprise Linux'. It does not trigger off the legacy OS type of 'Red Hat Enterprise Linux CoreOS'.

Identifying Red Hat Enterprise Linux CoreOS

Having triggers off an OS type of 'Red Hat Enterprise Linux', the pattern detects that the OS type is actually Red Hat Enterprise Linux CoreOS by searching for the word 'CoreOS' in the host's os_name or os_release attribute. End of Life data is then provided for Red Hat Enterprise Linux CoreOS rather than Red Hat Enterprise Linux.

Column Mappings

The column mappings between Red Hat and Discovery are as follows:

Red Hat Column

Discovery Column

Full support ends

Retirement Date

Maintenance support ends

End of Support Date

N/A

End of Security Support Date

Extended life cycle support (ELS) add-on ends

End Of Extended Support Date

Major or Minor Versions

The ELS dates relate to the major versioning level. However, should a customer wish to remain on a specific minor version for longer, an optional Extended Update Support (EUS) package can be purchased. This allows a customer to either receive EOL data at the major (ELS) versioning level (the default) or, upon setting a configuration option within the pattern, to receive EOL data at the minor (EUS) versioning level.

os_extended_update Attribute

There is a companion pattern that sets the ELS, EUS, EEUS or E4S status of a host running Red Hat Enterprise Linux. Having set the os_extended_update attribute on the host, the RHEL OS SupportDetail pattern then provides the corresponding EOL data.

Extended Support

The End of Extended Support Date attribute is intended to hold the theoretically “best” available date provided by any of the Red Hat subscription schemes. With having just a single End of Extended Support Date attribute, it is NOT possible for it to hold all the end of extended support dates provided by Red Hat under their various subscription schemes, be it ELS, EUS, EEUS or E4S:

Red Hat Subscription SchemeVersionApplicable End of Extended Support Date
EUS8.42023-05-31
E4S8.42025-05-31

If the host’s OS has a E4S subscription, its EOES date will be set to reflect this. If the host’s OS is not related to SAP in any way, any E4S-related date will be ignored when setting the EOES date.

End of Security Support Date

The End of Security Support Date attribute is used to hold the end of life date to which you are entitled having subscribed to a Red Hat subscription scheme for a given host.

If the EOES date and EOSS date end up holding the same date, the EOES date will always be set.

Example

VersionSubscription SchemeRetirement DateEnd of Support DateEnd of Security Support DateEnd of Extended Support Date
8.4 2021-11-302021-11-30[Not set as no subscription detected]2023-05-31 [As the host’s OS appears not to be related to SAP in any way, the E4S EOL date is ignored when setting the EOES date]
8.4EUS2021-11-302021-11-302023-05-31 [The date when support actually comes to an end for his host due to the EUS subscription]2023-05-31 [Due to the EUS subscription detected, EOES is set to the theoretically “best” available date that the EUS scheme provides]
8.4E4S2021-11-302021-11-302025-03-01 [The date when support actually comes to an end for his host due to the E4S subscription]2025-03-01 [Due to the E4S subscription detected, EOES is set to the theoretically “best” available date that the E4S scheme provides]

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Discovery content reference