Description of problem:
Pipeline build keeps new status after upgrade jenkins server from 4.4 to 4.5
And failed to sync pipeline build from cli client and jenkins webconsole.
Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-06-08-083627 -> 4.5.0-rc.1
Steps to Reproduce:
1.Prepare jenkins server and pipeline build(https://github.com/openshift/origin/tree/master/examples/jenkins/pipeline) in 4.4 cluster
2.Upgrade 4.4 cluster to 4.5
3.Trigger pipeline build again.
The pipeline build is triggered from cli client keeps in new status.
The pipelibe build is triggered from jenkins webconsole keeps in running, and don't sync to cli side.
oc get builds
NAME TYPE FROM STATUS STARTED DURATION
sample-pipeline-1 JenkinsPipeline Complete 4 hours ago
nodejs-mongodb-example-1 Source Git@a096bd2 Complete 4 hours ago 1m16s
openshift-jee-sample-1 JenkinsPipeline Complete 4 hours ago
openshift-jee-sample-docker-1 Docker Binary Complete 4 hours ago 1m5s
openshift-jee-sample-2 JenkinsPipeline Complete 2 hours ago
sample-pipeline-2 JenkinsPipeline Complete 2 hours ago
nodejs-mongodb-example-2 Source Git@a096bd2 Complete 2 hours ago 1m17s
openshift-jee-sample-docker-2 Docker Binary Complete 2 hours ago 1m7s
sample-pipeline-3 JenkinsPipeline New
openshift-jee-sample-3 JenkinsPipeline New
New pipeline builds could go to completed.
Created attachment 1696453 [details]
jenkins pod log
will be cherrry picked for 4.5
The OPENSHIFT_JENKINS_IMAGE_VERSION in the Jenkins 4.5 image was incorrectly set to 4.0, hence, the old plugins coming to 4.4 were not fully overridden, letting the openshift-sync plugin missing the kubernetes-client and not working anymore.
The fix consist in aligning OPENSHIFT_JENKINS_IMAGE_VERSION .
A PR is baking for 4.6 and will be manually cherry-picked to 4.5
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.