Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trying to wrap my head around patching in Red Hat. Can anyone validate that my understanding here is correct?
Let's take RHEL 7.5 as an example. My options are:
1) Stay at 7.5 and patching nothing as EUS expired in April 2020
2) Patch to the latest version (7.8)
Now, if for some reason I need to stay at 7.5 due to app stack certification, I believe I would be SOL at this point, correct?
In other words, I see this "Maintenance 2" phase on Red Hat's site which runs up until 2024, but am I correct to say that this maintenance phase ONLY applies to the last version of RHEL 7 (assuming 7.9)?
EUS repository Deactivation
For a given RHEL minor release EUS repository (for example RHEL 8.1), like all EUS repositories, will be retired 24 months after it is created and becomes available via Red Hat Subscription Manager. When an EUS repository reaches retirement, no new errata are released to the repositories. However, all previously released errata remain available to customers with an active subscription. It is imperative to migrate to a later EUS release to continue receiving errata updates like security and bug-fix errata.
You should patch to the latest available minor release whenever possible.
100%, just regarding those odd cases where an app may not be certified beyond a specific version.
That is an interesting question. Theoretical there should be no reason to avoid updating. The releases of RHEL 7.x series are strictly compatible with each other.
EUS allows the organization / company to stay on a minor version if required by a third party application which is only tested with a particular minor version of RHEL, such as Oracle Database, IBM DB2, IBM Cloud Orchestrator, hortonworks.
practically impossible to reach the 100 % [coompatibility]. Yes, I know. But again, if there was no real reason to keep you need to update. That was what you told in post #2.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.