What's the future of CentOS 7 support?
With the December 2020 announcement that Red Hat was going to discontinue CentOS 8 at the end of 2021 (a shocking 8 years ahead of the stated end of life), many folks are wondering if there is any impact to CentOS 7 support.
In this blog, we discuss the impact of that announcement on CentOS 7, look at the current status of CentOS 7 support options, and discuss the long-term support outlook for those using this popular Enterprise Linux distribution.
To answer the question at the beginning of the article, the short answer is, no, there's no impact to CentOS 7 as a result of the December Red Hat announcement. Or, at least, nothing has been announced that would indicate that there will be any impact. Red Hat continues to publish the date of June 30, 2024 as the end of Maintenance Support for RHEL 7, the upstream for CentOS 7.
RHEL 7 was released on June 10, 2014, so the June 2024 EOL date for CentOS 7 is the full 10 years that we expected.
What Happened to CentOS and What to Do NextIn this webinar from Perforce OSS Evangelist Javier Perez, he discusses the changes to CentOS EOL dates, why they were made, and how organizations can prepare for what's next.
In this webinar from Perforce OSS Evangelist Javier Perez, he discusses the changes to CentOS EOL dates, why they were made, and how organizations can prepare for what's next.
Yes, CentOS 7 is one of the two current releases of CentOS Linux: CentOS Linux 7 and CentOS Linux 8. Both versions of CentOS Linux continue to receive security patches and bug fix updates.
CentOS Linux 7 has gone through several phases in its lifecycle though, and we are currently in the “Maintenance Support 2” phase where only what Red Hat considers to be critical and import security patches and urgent priority bugfixes are released.
This product will remain in this phase until it reaches End-of-Life. The phase began in August 2020 and took CentOS 7 out of “Maintenance Phase 1” which, along with General Availability, is where most of the changes including minor releases occur.
CentOS Linux 7 will reach end of life on June 30, 2024, the same date that RHEL 7 enters the next vendor support phase: RHEL 7 Extended Lifecycle Support. After this date, CentOS 7 will no longer receive any security updates or bugfixes from Red Hat.
For all intents and purposes, CentOS 7 will no longer receive support from the community. Most, if not all, support requests directed at the community for end of life CentOS releases will be answered with the equivalent of, “That version of CentOS is EOL. Please upgrade to a newer distribution.”
We don’t anticipate or expect any changes to the CentOS 7 EOL date but, honestly, we didn’t expect to see CentOS Linux 8 support shortened by 8 years either. It is always possible that Red Hat will make another announcement and shorten the CentOS 7 lifecycle, but after the backlash of the CentOS 8 announcement, I would be highly surprised to hear of a reduced lifecycle for CentOS 7.
With CentOS 7 being current, there are several support options, including vendor support for the upstream product (RHEL7) through Red Hat, upstream package maintainer support for the packages included in EL7, community (aka peer) support, and commercial support.
Red Hat supports CentOS 7 through bug reports filed against RHEL 7 in Bugzilla.
Bugs filed in Bugzilla don’t always get the attention that many of us think that they should receive, but at least the problem is documented for others encountering the same problem.
Should your issue be addressed by Red Hat, don’t expect a quick turnaround — unless it is something they consider high priority. Often times solutions (links to upstream patches, directly submitted patches, etc.) that are provided take many months to be included in a RHEL release. If the version of RHEL that you filed the bug against is no longer the current minor release, you may find the ticket getting closed without resolution.
That being said, it is good to be able to reference a Bugzilla issue when reporting the issue through the other support channels.
You can also submit issues at the CentOS Bug Tracker but, unless the issue is directly related to CentOS, itself, and not an issue in the equivalent RHEL release, you will be told to submit the issue to Red Hat or the upstream project.
Sometimes the fastest way to get an issue resolved with a package is to take the issue directly to the programmers who maintain the original package that Red Hat includes with RHEL.
If the problem is not present in the version(s) that the maintainers publish, probably due to a configuration or code change implemented by Red Hat, the upstream folks will likely reject your support request.
When the problem is present in the original code, most projects want to hear about the issue directly. The people responsible for the projects often have a reputation to uphold, even if it’s only the reputation of the project and not for themselves.
The up-side to upstream support is that issues can usually be resolved faster than the upstream vendor support option, provided that the project is being actively developed. The downside is that Red Hat is not likely to incorporate a fix from the package upstream in a future update or release any time soon unless they rebase the package on a newer version.
Another support channel is Community support, aka Peer support. This method can be hit or miss because it is the equivalent of casting your question out to a large group of people without knowing the background of the respondents or the quality of the response that you reel back into shore.
Community support can be obtained through mailing lists, chat/IRC servers or online groups such as the vast expanse of StackExchange sites.
If the problem is commonly encountered or you happen to catch the eye of someone who knows exactly what is wrong, or at least how to troubleshoot the issue properly, community support can be a wonderful option.
On the other hand, an uncommon (or never-seen-before) issue can result in little (or no) response, delayed responses, wrong responses or accidental misinformation.
The people responding to community support requests often have a genuine desire to help you, but they have no real investment into resolving your problem.
Commercial support is one of the primary differentiators between RHEL and CentOS Linux.
Many RHEL subscriptions include commercial support with response SLAs, but the costs can be prohibitive. Avoiding the substantial costs associated with RHEL is one of the primary reasons that CentOS Linux is so popular.
“CentOS 7 is a current release, so I’ll just go to Red Hat and purchase support from them,” you say? Well, Red Hat will tell you that CentOS 7 is not a supported product and that you need to convert your systems over to RHEL 7 or 8 to receive support. You are now tied into their subscription model moving forward.
This is where 3rd party commercial support for CentOS 7 from a company like OpenLogic can be an excellent option.
OpenLogic presently includes CentOS 7 in our “Enterprise Linux Support – Enhanced” offering. With our ELS – Enhanced support, our team of Tier 3 and Tier 4 architects and engineers can troubleshoot your CentOS 7 issues, whether it is a problem with one package, the entire system, or interoperability with other OSS packages.
If we determine the problem to be a bug or security flaw, we can file the necessary bug reports with both upstream package maintainers and as well as coordinate invoking community support and vetting the responses.
Once made aware of such a problem, we begin work on developing a solution.
Many times, the OpenLogic team will file a new report and soon thereafter submit a patch to resolve the issue. By giving back to OSS projects, we not only solve the problem for our customers today, but also help solve the problem for all of the users of that particular project.
Once a solution is available, we can immediately build an updated CentOS 7 package that includes the fix, sign it via GPG and publish it for our customers.
We’ve found that this multi-faceted approach provides the best value to our customers and the OSS community as a whole. Our customers get an updated package as soon as we verify the fix without waiting for the patch to trickle down from where it was fixed upstream to a RHEL package update and they can get a CentOS package update, should one ever be provided.
OpenLogic will continue to support CentOS 7 after EOL through our “Enterprise Linux Support – Enhanced LTS” offering, regardless of the actual EOL date. With our “ELS – Enhanced LTS”, OpenLogic will support your CentOS 7 systems for up to 5 additional years so you don’t have to worry about your support requests being shrugged off by the upstream or community simply because the version of CentOS is no longer current.
TALK TO A Centos EXPERT
There are many reasons to run CentOS Linux 7, and the fear of being left without supportable infrastructure should not be a reason to avoid CentOS 7.
Regardless of what happens to CentOS 7, OpenLogic’s CentOS Linux 7 support will be available for 5+ years to extend the life of your systems until you have had the opportunity to upgrade them.
OpenLogic can help with migrations and upgrades, too. Whether you are migrating from CentOS Linux 7 to another Enterprise Linux distribution (such as Oracle Linux or Ubuntu), to one of the emerging RHEL-rebuild distros (like AlmaLinux or Rocky Linux) or from CentOS Linux 6 to CentOS Linux 7 or 8, our teams support a vast ecosystem of OSS projects. We know how they interoperate and how to maximize your resources while minimizing the risks associated with change.
Speak with an expert today to see how we can help support your project.
TALK TO AN EXPERT
Enterprise Solutions Architect, OpenLogic by Perforce
Vince has worked in the IT industry for 27 years, as a C developer, a systems administrator, a DBA, and a network engineer. He focuses on infrastructure architecture and open source server technologies, ranging from web servers to authorization technologies like LDAP.
Enterprise Linux Developer, OpenLogic by Perforce
Rich Alloway has over 25 years of professional Linux experience in academic, Internet service provider and telco carrier environments. He has filled many production roles: SysAdmin, Systems/Network/RF Engineer and CTO. He is currently a member of the Enterprise Linux Team at OpenLogic by Perforce, and serves as a contributor on the Rocky Linux QA and Testing Team.