# End of life operating systems **URL:** \ **Category:** Using Jenkins\ **Tags:** sig-docs, sig-platform\ **Created:** [May 26, 2023, 6:00pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644 "2023-05-26T18:00:44Z")\ **Posts on this page:** 17\ **Page:** 2
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [September 25, 2023, 1:58pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/21 "2023-09-25T13:58:53Z")
> [@marklenders](#): > > I have several agents connected to the controller, some of them running CentOS7. > If I upgrade the controller to RHEL8 will the CentOS7 agents still continue to work or will I necessarily have to migrate them to RHEL8 as well? Nov 16, 2023 is the end of Red Hat Enterprise Linux 7 and CentOS 7 support by the Jenkins project for controllers and agents. June 30, 2024 is the end of public support for Red Hat Enterprise Linux 7 by Red Hat and the end of all support for CentOS 7. You should update your agents to a supported operating system. If you can’t do that, then you’ll need to test each upgrade yourself to see that it does not break your agents running CentOS 7. I’m confident that there is a way to run Java 7 on RHEL 8 and its derivatives, even if there is not an RPM package that can be used for the installation. ---
**Author:** ![Yeroc](https://avatars.discourse-cdn.com/v4/letter/y/65b543/32.png) [@Yeroc](https://community.jenkins.io/u/Yeroc)\ **Post date:** [November 17, 2023, 11:38pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/22 "2023-11-17T23:38:51Z")
This caught me off guard since our controller isn’t affected but our agents **are** running CentOS 7 and we didn’t get any advance warning on this until I read the changes for the latest LTS release! Is there an enhancement request somewhere for future releases so that advance warning is provided when the OS the agent(s) are running on has been deprecated or support is due to be dropped? ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [November 18, 2023, 12:14am UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/23 "2023-11-18T00:14:37Z")
> [@Yeroc](#): > > Is there an enhancement request somewhere for future releases so that advance warning is provided when the OS the agent(s) are running on has been deprecated or support is due to be dropped? That’s a good suggestion, though I think it might be better done in the [versions node monitors plugin](https://plugins.jenkins.io/versioncolumn/) than in Jenkins core. You’re welcome to submit an [enhancement request](https://www.jenkins.io/participate/report-issue/redirect/#15927). You’re also welcome to submit a pull request to implement the enhancement 😄 I think that it is better suited to the plugin because agents come and go and an administrative monitor persists until it is cleared. It might be unclear to the user when an ephemeral agent appears, has an unsupported operating system, then disappears, but the administrative monitor persists. You may also want to read the Jenkins blog post where we announced that change in May 2023. > **[End of life operating systems](https://www.jenkins.io/blog/2023/05/30/operating-system-end-of-life/)** > > Jenkins – an open source automation server which enables developers around the world to reliably build, test, and deploy their software ---
**Author:** ![martin-rust](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/martin-rust/32/6135_2.png) [@martin-rust](https://community.jenkins.io/u/martin-rust)\ **Post date:** [November 20, 2023, 1:38pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/24 "2023-11-20T13:38:02Z")
Jenkins 2.414.3 just cautions me that “Jenkins will no longer support Linux after **2099-12-31** ”. It’s a Jenkins WAR deployment inside Tomcat 9.0.82, OpenJDK 11, Fedora 38. And, yes, the system date is set correctly 😉 If you want to debug this, tell if you need additional information. ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [November 20, 2023, 2:43pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/25 "2023-11-20T14:43:49Z")
> [@martin-rust](#): > > If you want to debug this, tell if you need additional information. We’ll definitely need more information. It is best to provide detailed information as a bug report to [https://issues.jenkins.io/](https://issues.jenkins.io/) I attempted to duplicate the problem with the following Dockerfile: ```auto FROM fedora:38 RUN curl -o /etc/yum.repos.d/jenkins.repo https://pkg.jenkins.io/redhat-stable/jenkins.repo RUN rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io-2023.key RUN dnf upgrade -y RUN dnf install -y fontconfig java-11-openjdk RUN dnf install -y jenkins RUN curl -L -o /tmp/jenkins-2.414.3.war https://get.jenkins.io/war-stable/2.414.3/jenkins.war USER jenkins ENTRYPOINT java -jar /tmp/jenkins-2.414.3.war ``` I built and ran that Dockerfile with the command: ```auto $ docker build -t sample:1 . $ docker run --rm -p 8080:8080 -i -t sample:1 ``` I opened that Jenkins page from that machine in my web browser and confirmed that the end of life admin monitor displayed as follows: ![fedora-38-end-of-life](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/d/d809f22454e5d19a91f60cd716a81fe8981100fe.png) That output is what I expected to see, since Fedora 38 is end of life as of 18 May 2024. ---
**Author:** ![martin-rust](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/martin-rust/32/6135_2.png) [@martin-rust](https://community.jenkins.io/u/martin-rust)\ **Post date:** [November 21, 2023, 10:30am UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/26 "2023-11-21T10:30:37Z")
After upgrading to Jenkins 2.426.1, the notice has changed to the one just shown in your screenshot (which makes sense). So, I’ll regard this as fixed. Thanks. ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [January 13, 2024, 3:44am UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/27 "2024-01-13T03:44:21Z")
I’ve submitted an [update to the end of life operating system data](https://github.com/jenkinsci/jenkins/pull/8864) that adds data for: - Alpine Linux 3.19 - end of life Nov 1, 2025, 6 months after Alpine Linux 3.18 - Amazon Linux 2 - already end of life because it is a Red Hat Enterprise Linux 7 derivative - Amazon Linux 2023 - end of life Mar 15, 2028 - Fedora Linux 39 - end of life Dec 7, 2024, 6 months after Fedora Linux 38 ![amazon-linux-2-not-supported](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/a/a758878cf3baddf1e84f3871fdbcc9119a277f41.png) ---
**Author:** ![mcollier](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@mcollier](https://community.jenkins.io/u/mcollier)\ **Post date:** [March 19, 2024, 10:19pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/28 "2024-03-19T22:19:04Z")
I clicked on the Ignore button on this dialog so it no longer shows the warning. Is there a way to get the warning to reappear after Ignore has been clicked? Thanks, MIke ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [March 19, 2024, 10:49pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/29 "2024-03-19T22:49:29Z")
> [@mcollier](#): > > Is there a way to get the warning to reappear after Ignore has been clicked? From “Manage Jenkins” → “System” → “Administrative monitors configuration” there is a drop down list “Administrative monitors” that includes a checkbox for each administrative monitor. Enable the checkbox for “Operating system end of life monitor”. ---
**Author:** ![mcollier](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@mcollier](https://community.jenkins.io/u/mcollier)\ **Post date:** [March 19, 2024, 11:58pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/30 "2024-03-19T23:58:53Z")
Hi Mark, I have looked in the “Manage Jenkins” and I don’t see anything with the title “Administrative monitors configuration”. Here are all the categories I see in my Jenkins: ## System Configuration System Configure global settings and paths. Tools Configure tools, their locations and automatic installers. Plugins Add, remove, disable or enable plugins that can extend the functionality of Jenkins. Nodes Add, remove, control and monitor the various nodes that Jenkins runs jobs on. Clouds Add, remove, and configure cloud instances to provision agents on-demand. Appearance Configure the look and feel of Jenkins Managed files e.g. settings.xml for maven, central managed scripts, custom files, … ## Security Security Secure Jenkins; define who is allowed to access/use the system. Credentials Configure credentials Credential Providers Configure the credential providers and types Users Create/delete/modify users that can log in to this Jenkins. In-process Script Approval Allows a Jenkins administrator to review proposed scripts (written e.g. in Groovy) which run inside the Jenkins process and so could bypass security restrictions. ## Status Information Monitoring of Jenkins instance Monitoring of memory, cpu, http requests and more in the Jenkins instance. Monitoring of Jenkins agents Monitoring of builds, build queue and Jenkins agents. System Information Displays various environmental information to assist trouble-shooting. System Log System log captures output from `java.util.logging` output related to Jenkins. Load Statistics Check your resource utilization and see if you need more computers for your builds. About Jenkins See the version and license information. ## Troubleshooting Manage Old Data Scrub configuration files to remove remnants from old plugins and earlier versions. ## Tools and Actions Reload Configuration from Disk Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk. Jenkins CLI Access/manage Jenkins from your shell, or from your script. Script Console Executes arbitrary script for administration/trouble-shooting/diagnostics. Prepare for Shutdown Stops executing new builds, so that the system can be eventually shut down safely. ## Uncategorized Gerrit Trigger Triggers builds on Gerrit Events I’m running Jenkins 2.440.1 on RedHat 7.9 Thanks, Mike ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [March 20, 2024, 1:01am UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/31 "2024-03-20T01:01:45Z")
Poor typing on my part. From “Manage Jenkins” → “System” → “Administrative monitors configuration” is the path to the configuration. ---
**Author:** ![mcollier](https://avatars.discourse-cdn.com/v4/letter/m/59ef9b/32.png) [@mcollier](https://community.jenkins.io/u/mcollier)\ **Post date:** [March 21, 2024, 11:08pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/32 "2024-03-21T23:08:38Z")
Hi Mark, I was able to turn back on the OS end of life monitor with the path you provided. It showed up again once I restarted Jenkins. I am in the process of switching to a supported OS. Thanks for your help, Mike ---
**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\ **Post date:** [March 22, 2024, 8:22am UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/33 "2024-03-22T08:22:17Z")
Thanks for your feedback, @mcollier. 👍 ---
**Author:** ![maustin85](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/maustin85/32/10927_2.png) [@maustin85](https://community.jenkins.io/u/maustin85)\ **Post date:** [October 15, 2024, 2:55pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/34 "2024-10-15T14:55:29Z")
Im running jenkins 2.440.2 on Ubuntu 20.04. Why am i getting the message that Jenkins will stop supporting Linux on 2099-12-31. Ubuntu 20 not supported anymore? But year 2099? ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [October 15, 2024, 3:17pm UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/35 "2024-10-15T15:17:25Z")
> [@maustin85](#): > > I’m running Jenkins 2.440.2 on Ubuntu 20.04. Why am i getting the message that Jenkins will stop supporting Linux on 2099-12-31. Ubuntu 20 not supported anymore? But year 2099? Ubuntu 20.04 reaches its end of public support 2 Apr 2025. Jenkins is alerting you that the Jenkins project stops supporting an operating system when the upstream vendor ends their public support. The incorrect date is a bug ([JENKINS-73845](https://issues.jenkins.io/browse/JENKINS-73845)). Unfortunately, it is a bug that I am unable to duplicate. If you can provide more details so that the bug can be duplicated, I’m happy to look for a fix. ---
**Author:** ![Nishan440](https://avatars.discourse-cdn.com/v4/letter/n/77aa72/32.png) [@Nishan440](https://community.jenkins.io/u/Nishan440)\ **Post date:** [October 30, 2024, 6:20am UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/36 "2024-10-30T06:20:28Z")
![Screenshot_2024-10-30_11-49-17](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/7/7323b5461749c66dffc35f3e75e260cd871779e0.png) what i can do can anyone suggest should i upgrade or not 😅 ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [October 30, 2024, 11:05am UTC](https://community.jenkins.io/t/end-of-life-operating-systems/7644/37 "2024-10-30T11:05:45Z")
> [@Nishan440](#): > > should i upgrade or not 😅 😅 Yes, you should upgrade. If you upgrade today to [Jenkins weekly 2.483](https://www.jenkins.io/changelog/2.483/), then you can confirm that the issue is fixed in that release. If you wait 24 hours and check the page again, you’ll see the correct end of life date without actually having the fix. The bug was an error in the date conditional. It has been fixed by @aburdajewicz [Previous page](https://community.jenkins.io/t/end-of-life-operating-systems/7644.md?page=1)