Bug 1845902
Summary: | [upgrade]Pipeline build keeps new status after upgrade jenkins server from 4.4 to 4.5 | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Akram Ben Aissi <abenaiss> | |
Component: | Jenkins | Assignee: | Akram Ben Aissi <abenaiss> | |
Status: | CLOSED ERRATA | QA Contact: | Jitendar Singh <jitsingh> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 4.5 | CC: | aos-bugs, jitsingh, pbhattac, vbobade, xiuwang | |
Target Milestone: | --- | |||
Target Release: | 4.5.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | 1845829 | |||
: | 1847452 (view as bug list) | Environment: | ||
Last Closed: | 2020-07-13 17:43:50 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1845829 | |||
Bug Blocks: | 1847442 |
Description
Akram Ben Aissi
2020-06-10 11:55:48 UTC
The reproducer for this one consists in a 4.5 cluster to start a Jenkins instance using the 4.4 image and then update the imagestream to point to 4.5 and ensure that no errors are in the logs and that a pipeline starts correctly: ## Tag 4.4 jenkins image $oc tag quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:bd8b955ae1fa10135c9904d85c60b20a8f06deda9f103c88a55e1d28f4cb19cb jenkins:2 --reference-policy='local' ##Create jenkins persistent pod $oc new-app jenkins-persistent -p NAMESPACE=$( oc project -q) ## Wait jenkins pod ready ## Tag 4.5 jenkins image $oc tag <jenkins-image-in-45> jenkins:2 --reference-policy='local' ## Wait jenkins pod ready ##Create pipeline build $oc new-app -f ~/go/src/github.com/openshift/origin/examples/jenkins/pipeline/maven-pipeline.yaml $oc start-build openshift-jee-sample Verified. 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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409 |