Recently , after the openshift cluster upgrade to ocp 4.15, some tenants asked about lack of update for Jenkins (stuck on version 2.401.1 , EOL LTS version)
Long story short (people can read https://pagure.io/centos-infra/issue/1409) :
- Openshift (during releases) modified the default jenkins imagestreamtag (https://access.redhat.com/documentation/en-us/openshift_container_platform/4...) - deployed jenkins pods were using DeploymentConfig using jenkins:2 imagestreamtag (not up2date)
What is required from you , CI tenants : you can just edit (for now) your deploymentconfig like this, and that will automatically trigger a pod redeploy, using latest jenkins lts version from registry ( v2.440.3 when writing this) :
``` oc edit dc/jenkins replace "name: jenkins:2" with "name: jenkins:ocp-upgrade-redeploy" and exit
```
Watch for your logs and then update your plugins
Worth knowing that we'll enforce this rule on June 17th, by making (ocp cluster wise in openshift namespace) jenkins:2 an alias to jenkins:ocp-upgrade-redeploy, so redeploying *all* jenkins pods that aren't migrated yet
Summary : So if you prefer to do that yourself and watch process, and pause your ci jobs, etc , do it now If you don't do it, it will be done automatically (but in unattended way) on June 17th
On 06/06/2024 17:19, Fabian Arrotin wrote:
Recently , after the openshift cluster upgrade to ocp 4.15, some tenants asked about lack of update for Jenkins (stuck on version 2.401.1 , EOL LTS version)
Long story short (people can read https://pagure.io/centos-infra/issue/1409) :
- Openshift (during releases) modified the default jenkins
imagestreamtag (https://access.redhat.com/documentation/en-us/openshift_container_platform/4...)
- deployed jenkins pods were using DeploymentConfig using jenkins:2
imagestreamtag (not up2date)
What is required from you , CI tenants : you can just edit (for now) your deploymentconfig like this, and that will automatically trigger a pod redeploy, using latest jenkins lts version from registry ( v2.440.3 when writing this) :
oc edit dc/jenkins replace "name: jenkins:2" with "name: jenkins:ocp-upgrade-redeploy" and exit
Watch for your logs and then update your plugins
Worth knowing that we'll enforce this rule on June 17th, by making (ocp cluster wise in openshift namespace) jenkins:2 an alias to jenkins:ocp-upgrade-redeploy, so redeploying *all* jenkins pods that aren't migrated yet
Summary : So if you prefer to do that yourself and watch process, and pause your ci jobs, etc , do it now If you don't do it, it will be done automatically (but in unattended way) on June 17th
Erratum : I'll do that on June 19th instead (giving more or less two weeks timeframe)
Hi Fabian,
The DeploymentConfig for Jenkins in the ceph-csi Namespace was updated last week. Is there an other step required to trigger the update? I don't think our Jenkins got redeployed yet, it is still on version 2.401.1.
Thanks, Niels
On Thu, 2024-06-06 at 17:19 +0200, Fabian Arrotin wrote:
Recently , after the openshift cluster upgrade to ocp 4.15, some tenants asked about lack of update for Jenkins (stuck on version 2.401.1 , EOL LTS version)
Long story short (people can read https://pagure.io/centos-infra/issue/1409) :
- Openshift (during releases) modified the default jenkins
imagestreamtag ( https://access.redhat.com/documentation/en-us/openshift_container_plat form/4.15/html-single/jenkins/index#relocation-of-openshift-jenkins- images_important-changes-to-openshift-jenkins-images)
- deployed jenkins pods were using DeploymentConfig using jenkins:2
imagestreamtag (not up2date)
What is required from you , CI tenants : you can just edit (for now) your deploymentconfig like this, and that will automatically trigger a pod redeploy, using latest jenkins lts version from registry ( v2.440.3 when writing this) :
oc edit dc/jenkins replace "name: jenkins:2" with "name: jenkins:ocp-upgrade-redeploy" and exit
Watch for your logs and then update your plugins
Worth knowing that we'll enforce this rule on June 17th, by making (ocp cluster wise in openshift namespace) jenkins:2 an alias to jenkins:ocp-upgrade-redeploy, so redeploying *all* jenkins pods that aren't migrated yet
Summary : So if you prefer to do that yourself and watch process, and pause your ci jobs, etc , do it now If you don't do it, it will be done automatically (but in unattended way) on June 17th
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
On 10/06/2024 09:04, Niels de Vos wrote:
Hi Fabian,
The DeploymentConfig for Jenkins in the ceph-csi Namespace was updated last week. Is there an other step required to trigger the update? I don't think our Jenkins got redeployed yet, it is still on version 2.401.1.
Thanks, Niels
OH !
Erratum : it should be jenkins:scheduled-upgrade-redeploy and not jenkins:ocp-upgrade-redeploy : wrong copy/paste when I sent the mail last week, sorry
switching to jenkins:scheduled-upgrade-redeploy should point to latest and automatically redeploy pods
On Thu, 2024-06-06 at 17:19 +0200, Fabian Arrotin wrote:
Recently , after the openshift cluster upgrade to ocp 4.15, some tenants asked about lack of update for Jenkins (stuck on version 2.401.1 , EOL LTS version)
Long story short (people can read https://pagure.io/centos-infra/issue/1409) :
- Openshift (during releases) modified the default jenkins
imagestreamtag ( https://access.redhat.com/documentation/en-us/openshift_container_plat form/4.15/html-single/jenkins/index#relocation-of-openshift-jenkins- images_important-changes-to-openshift-jenkins-images)
- deployed jenkins pods were using DeploymentConfig using jenkins:2
imagestreamtag (not up2date)
What is required from you , CI tenants : you can just edit (for now) your deploymentconfig like this, and that will automatically trigger a pod redeploy, using latest jenkins lts version from registry ( v2.440.3 when writing this) :
oc edit dc/jenkins replace "name: jenkins:2" with "name: jenkins:ocp-upgrade-redeploy" and exit
Watch for your logs and then update your plugins
Worth knowing that we'll enforce this rule on June 17th, by making (ocp cluster wise in openshift namespace) jenkins:2 an alias to jenkins:ocp-upgrade-redeploy, so redeploying *all* jenkins pods that aren't migrated yet
Summary : So if you prefer to do that yourself and watch process, and pause your ci jobs, etc , do it now If you don't do it, it will be done automatically (but in unattended way) on June 17th
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
CI-users mailing list -- ci-users@lists.centos.org To unsubscribe send an email to ci-users-leave@lists.centos.org
On Mon, 2024-06-10 at 11:22 +0200, Fabian Arrotin wrote:
On 10/06/2024 09:04, Niels de Vos wrote:
Hi Fabian,
The DeploymentConfig for Jenkins in the ceph-csi Namespace was updated last week. Is there an other step required to trigger the update? I don't think our Jenkins got redeployed yet, it is still on version 2.401.1.
Thanks, Niels
OH !
Erratum : it should be jenkins:scheduled-upgrade-redeploy and not jenkins:ocp-upgrade-redeploy : wrong copy/paste when I sent the mail last week, sorry
switching to jenkins:scheduled-upgrade-redeploy should point to latest and automatically redeploy pods
Thanks!
In the logs I now see this message:
2024-06-10 10:15:50 INFO hudson.PluginManager loadDetachedPlugins Upgrading Jenkins. The last running version was 2.401.1. This Jenkins is version 2.440.3.
Cheers, Niels
On Thu, 2024-06-06 at 17:19 +0200, Fabian Arrotin wrote:
Recently , after the openshift cluster upgrade to ocp 4.15, some tenants asked about lack of update for Jenkins (stuck on version 2.401.1 , EOL LTS version)
Long story short (people can read https://pagure.io/centos-infra/issue/1409) :
- Openshift (during releases) modified the default jenkins
imagestreamtag ( https://access.redhat.com/documentation/en-us/openshift_container_plat form/4.15/html-single/jenkins/index#relocation-of-openshift- jenkins- images_important-changes-to-openshift-jenkins-images)
- deployed jenkins pods were using DeploymentConfig using
jenkins:2 imagestreamtag (not up2date)
What is required from you , CI tenants : you can just edit (for now) your deploymentconfig like this, and that will automatically trigger a pod redeploy, using latest jenkins lts version from registry ( v2.440.3 when writing this) :
oc edit dc/jenkins replace "name: jenkins:2" with "name: jenkins:ocp-upgrade- redeploy" and exit
Watch for your logs and then update your plugins
Worth knowing that we'll enforce this rule on June 17th, by making (ocp cluster wise in openshift namespace) jenkins:2 an alias to jenkins:ocp-upgrade-redeploy, so redeploying *all* jenkins pods that aren't migrated yet
Summary : So if you prefer to do that yourself and watch process, and pause your ci jobs, etc , do it now If you don't do it, it will be done automatically (but in unattended way) on June 17th
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
CI-users mailing list -- ci-users@lists.centos.org To unsubscribe send an email to ci-users-leave@lists.centos.org
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
Hey,
Thanks for the heads up (and apologies for the delay). I finally upgraded our (systemd) Jenkins and it's now sitting on 2.440.3. Although, it now complains about:
You are running Jenkins on Java 11, support for which will end on or after Sep 30, 2024. Refer to the documentation for more details.
I guess you can never win ;)
Also, while redeploying the Jenkins pod it somehow managed to nuke the entire clouds section, but thankfully I had a backup of our config.xml at hand. After copying the missing section back into the live configuration (and restarting Jenkins) everything seems to be in order.
On 6/6/24 17:19, Fabian Arrotin wrote:
Recently , after the openshift cluster upgrade to ocp 4.15, some tenants asked about lack of update for Jenkins (stuck on version 2.401.1 , EOL LTS version)
Long story short (people can read https://pagure.io/centos-infra/issue/1409) :
- Openshift (during releases) modified the default jenkins imagestreamtag (https://access.redhat.com/documentation/en-us/openshift_container_platform/4...)
- deployed jenkins pods were using DeploymentConfig using jenkins:2 imagestreamtag (not up2date)
What is required from you , CI tenants : you can just edit (for now) your deploymentconfig like this, and that will automatically trigger a pod redeploy, using latest jenkins lts version from registry ( v2.440.3 when writing this) :
oc edit dc/jenkins replace "name: jenkins:2" with "name: jenkins:ocp-upgrade-redeploy" and exit
Watch for your logs and then update your plugins
Worth knowing that we'll enforce this rule on June 17th, by making (ocp cluster wise in openshift namespace) jenkins:2 an alias to jenkins:ocp-upgrade-redeploy, so redeploying *all* jenkins pods that aren't migrated yet
Summary : So if you prefer to do that yourself and watch process, and pause your ci jobs, etc , do it now If you don't do it, it will be done automatically (but in unattended way) on June 17th
CI-users mailing list -- ci-users@lists.centos.org To unsubscribe send an email to ci-users-leave@lists.centos.org
On 06/06/2024 17:19, Fabian Arrotin wrote:
Recently , after the openshift cluster upgrade to ocp 4.15, some tenants asked about lack of update for Jenkins (stuck on version 2.401.1 , EOL LTS version)
Long story short (people can read https://pagure.io/centos-infra/issue/1409) :
- Openshift (during releases) modified the default jenkins
imagestreamtag (https://access.redhat.com/documentation/en-us/openshift_container_platform/4...)
- deployed jenkins pods were using DeploymentConfig using jenkins:2
imagestreamtag (not up2date)
What is required from you , CI tenants : you can just edit (for now) your deploymentconfig like this, and that will automatically trigger a pod redeploy, using latest jenkins lts version from registry ( v2.440.3 when writing this) :
oc edit dc/jenkins replace "name: jenkins:2" with "name: jenkins:ocp-upgrade-redeploy" and exit
Watch for your logs and then update your plugins
Worth knowing that we'll enforce this rule on June 17th, by making (ocp cluster wise in openshift namespace) jenkins:2 an alias to jenkins:ocp-upgrade-redeploy, so redeploying *all* jenkins pods that aren't migrated yet
Summary : So if you prefer to do that yourself and watch process, and pause your ci jobs, etc , do it now If you don't do it, it will be done automatically (but in unattended way) on June 17th
As I was away in the last two days, it was implemented earlier today so all CI tenants should be running jenkins 2.440.3 now