Bug 1364949
| Summary: | jenkinspipeline builds skip running status in openshift client after restart master api server | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | XiuJuan Wang <xiuwang> |
| Component: | ImageStreams | Assignee: | Jimmi Dyson <jdyson> |
| Status: | CLOSED ERRATA | QA Contact: | Wang Haoran <haowang> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | aos-bugs, bparees, dyan, jokerman, mmccomas, pweil, tdawson |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: API server restart causes the Jenkins sync plugin to lose its connection to OpenShift
Consequence: Pipeline builds are not properly executed in the Jenkins server
Fix: Update sync plugin to handle connection loss when API server is restarted
Result: Builds will be properly processed by the sync plugin and executed in Jenkins if the API server is restarted
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-18 12:52:08 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: | |||
|
Description
XiuJuan Wang
2016-08-08 09:31:58 UTC
also tracking as: https://github.com/fabric8io/openshift-jenkins-sync-plugin/issues/99 This is a problem if the API server host is rebooted. If the API server process is stopped/started then it reconnects fine. This is a TCP timeout issue that affects oc client too (try it with `oc get pods -w` & then force reboot the API server - notice no timeout). I'm looking at implementing WS pings but not sure if API server supports pings (it should if it's spec compliant). This is a fix in kubernetes-client - PR https://github.com/fabric8io/kubernetes-client/pull/517. Will release client after merged & update jenkins plugin with new version after that. I've released openshift-jenkins-sync-plugin 0.0.13 (https://repo.jenkins-ci.org/releases/io/fabric8/jenkins/plugins/openshift-sync/0.0.13/) which should fix this issue. @bparees: Forgotten how to get the Jenkins image updated with this new version? centos image is available w/ the updated plugin. rhel has not been rebuilt yet. New jenkins-1 and jenkins-2 images have been built with the updated openshift-sync plugin. Verified brew-pulp.../openshift3/jenkins-1-rhel7 6f476676a4a1 openshift-sync 0.0.14 openshift v3.4.0.19+346a31d kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 Actual result: After restart master api,new triggered pipeline builds could be running status, then change to complete. 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-2017:0066 |