Bug 1451223
| Summary: | Failed to sync jenkins pipeline build status from openshift to jenkins job with jenkins-2-rhel7 and jenkins-1-rhel7 image | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dongbo Yan <dyan> | ||||
| Component: | ImageStreams | Assignee: | Ben Parees <bparees> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Dongbo Yan <dyan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.6.0 | CC: | aos-bugs, bparees, jokerman, mmccomas, smunilla | ||||
| Target Milestone: | --- | Keywords: | Regression | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause: When Kubernetes settings are updated, Jenkins is restarted/reloaded. This causes all of the configurations to be reloaded, including ours. credentialsId becomes null and causes NPE's to be thrown, stopping the watchers, which can't recover.
Consequence: When Kube is updated, we stop being able to sync with OpenShift
Fix: The getter for credentialsId check for null, and returns "" if so
Result: The bug does not occur, Kube can now be updated without NPE
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-08-10 05:24:06 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Dongbo Yan
2017-05-16 07:22:03 UTC
Ryan, this sounds like the issue you already own: https://github.com/openshift/jenkins-sync-plugin/issues/132 Fix merged here: https://github.com/openshift/jenkins-sync-plugin/pull/135 don't put it ON_QA until it's in an image that QE can test. next steps: 1) the plugin needs to be released (you/gabe) 2) the plugin needs to be RPM packaged (troy/sam) 3) the jenkins image needs to be updated to reference the new plugin version (you) 4) QE can test w/ the new centos image produced by (3) but ultimately the bug can't be validated until a new rhel image is built that consumes the rpm from (2). 2+3 can happen in parallel. Test with brew-pulp.../openshift3/jenkins-1-rhel7@sha256:a82dcb86416e13f5e66e4ad6f7c1e03a70431c4676028dfb7ee2172a8b9b0adb jenkins-plugin-openshift-pipeline-1.0.47-10.el7.x86_64 jenkins-plugin-openshift-login-0.12-10.el7.x86_64 jenkins-plugin-openshift-sync-0.1.23-10.el7.x86_64 could sync pipeline build status after modifying slave pod template in jenkins server could move to 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/RHEA-2017:1716 |