RHEL 6 and 7 EOL questions
According to this page
https://access.redhat.com/support/policy/updates/errata
RHEL 6 is going EOL 11/30/2020 and RHEL 7 going EOL 6/30/2024. But on further down it says that EUS - Extended Update Support ends for:
6.6 (ends October 31, 2016)
6.7 (ends July 31, 2017)
And RHEL 7
7.1 (ends March 31, 2017)
7.2 (ends November 30, 2017)
So what does all this actually mean? Does this mean that if we are using 6.6 we are not going to be able to get support after 10/2016 and no support for 6.7 after 7/2017 even though the product is not going EOL until 2020? Can someone explain this to me in laymens terms please? Because the way I see it, why do I need a subscription that includes EUS if RHEL 6 is not going EOL until 2020?
Responses
Extended Update Support (EUS) allows one to receive bugfix and security updates to a minor release (eg: the Y in RHEL X.Y) for a longer time.
EUS is intended to be used for customers who have a longer software lifecycle and require bug/security updates, but don't wish to update to each minor release as it comes out every 6-or-so months.
So when you see:
6.6 (ends October 31, 2016)
This means there is a separate RHEL channel for RHEL 6.6 EUS and we'll keep making bugfix/security updates into that channel until Oct 31 2016. After this date, you're welcome to stay on RHEL 6.6 if you wish but in the event that a software update is required to resolve an issue, you'll need to move to either the main RHEL 6 channel or a later RHEL 6.Y EUS release.
Full technical support for usage and configuration will be given to all RHEL 6 minor releases throughout the entire lifecycle until Nov 30 2020.
You could call up on that day with RHEL 6.0, ask us how to do something, and we'll help you do it. We'll also probably remind you that the product goes EOL that day and you really should be moving to a later major RHEL release.
Still don't get it. If I currently have 6.6 installations under corporate maintenance. When will my version be EOS and EOL? What does it mean that I will have to move to a different channel? Can you please be more specific?
We stopped making updates to 6.6 on October 31 2016, but have continued updating packages in later RHEL 6 minor releases.
Support for configuration and usage questions is provided on all RHEL 6 until at least November 30 2020 (the end of the Production 3 phase), but if you run into an issue with your currently-installed 6.6 packages, you'll need to update to a package from a later minor release in the main RHEL 6 channel if available, or we may choose to deliver the fix in later major release such as RHEL 7.
The main RHEL 6 channel stops getting updates on November 30 2020 (the end of the Production 3 Phase). If you choose to purchase the RHEL 6 Extended Lifecycle Support to get the critical errata delivered during the ELS phase, you'll need to add the ELS channel to your systems. If you choose not to purchase ELS after 2020, then you won't be getting any more package updates so there's no need to change channel.
Guru
12851 points
All,
To add to Jamie's last post.
EUS is not needed, but it means you will always update to the current minor release of RHEL and the latest patch level of the rpm you update.
E.g. If you do not buy EUS today and therefor do not connect to RHEL 6.6 EUS channels yum -y update will cause a full update to RHEL 6.9 with patches upto the last available patches.
ELS is only needed if the applications running on your server are not certified for a higher major release at the time the major release you are running at the end of Production phase 3. E.g. If you migrate before November 30 2020 to RHEL 7.x or RHEL 8.y there is no need to buy ELS.
Regards.
Jan Gerrit
I have a situation where I am running version. I need to have an advise what is the impact of not upgrading to the latest minor release. I will still get support by RedHat in case of issues, correct? Can I assume the only impact is that I am not running the latest package enhancements and bug fixes ?
Correct.
If you are running RHEL 6.0 and you ask "how do I do this?" then we will gladly help you configure it.
However, if you are running RHEL 6.0 and you say "I have this problem" and that problem is resolved with a package update from a later version of RHEL 6, then the answer is to upgrade that package and its dependencies.
Guru
12851 points
Hi Hristo,
You may run into issues where Red Hat will tell you that only an upgrade to the latest minor release wil fix it. Security issues are your biggest treath.
Regards,
Jan Gerrit
Hi, where could is find latest update to the document https://access.redhat.com/support/policy/updates/errata
I am trying to look for which minor release of 6.x is current supported via base channel ? Is it 6.8 and up ?
Another question, for example 6.7 EUS ends December 31, 2018 but when its standard base supported ended ? when will 6.8 standard support ends ?
thanks
The base channel always includes the latest packages for the latest minor release, so currently it contains 6.10.
Regardless of whether a system is subscribed to the base channel or one of the EUS channels, that system has tech support for usage and configuration until the EOL of the major release.
However, to get updated packages, the system must be subscribed to a channel which is receiving updates.
The only RHEL6 channels receiving updates are the base channel, and 6.7 EUS (until December 31 2018).
There is no EUS for 6.8 onwards.
Hello,
Could you confirm the following understanding is correct,
RHEL 7.6 is realased on 2018-10-30 and hence only based channel 7.6 will receive errata updates and no errata u will be provided on base channel of 7.5 or lower.
Likewise for RHEL 6, we should update to 6.10 to get the all the erratas
So the strategy to well maintain a RHEL release is to updates to latest minor release as soon as its available.
thanks
Hi, is there any plan to extend RHEL 6 beyond 30 Nov ?
No, but please see above about the difference between actual "End of Life" (which isn't happening) and the "Extended Life Phase" (which is happening).
There is also a much more detailed thread at: Red-Hat-Linux-6 END OF MAINTENANCE support II ENDS November 2020, Prepare to migrate to a supported version of RHEL
Hi, Do we need to be at RHEL 6.10 to get "Extended Lifecycle Support" (ELS). Or servers at RHEL 6.9 are acceptable as well.
You can get ELS with 6.9 or an earlier minor release. However, if we're troubleshooting a new issue which hasn't been seen before, it's likely we could ask you to test the latest packages. So updating as much as you can would be a good preventative step.
If you need a package update which is already available in 6.10 then you'll need to update to that package and any dependencies. There are no more updates to earlier minor releases like 6.9 or 6.8 or earlier.
If you need a package update which is available in the ELS channel, then you need the ELS entitlement to access the package.
Hi Team, Please let me know the procedure to avail ELS (Extended Lifecycle Support) for RHEL 6.10 server Or Please share the procedure to subscribe to ELS for RHEL 6.10 Server.
Thanks, Vivek
Community Member
52 points
From: https://access.redhat.com/support/policy/updates/errata#Extended_Update_Support
Note: Only Standard or Premium subscriptions to RHEL Server are eligible for ELS Support. RHEL Desktop or RHEL Workstation subscriptions are not eligible for ELS
If procurement bought a bunch of workstation, or a bunch of "self-service" licenses then those aren't going to be sufficient for the RHEL6 hosts after 30-Nov-2020. The license type has to be for Server, and has to be either Standard or Premium support level. So, either $1048 or $1299 per host, per year. Also, you probably want the response time and support hours the Premium subscription provides.