Bug 1721847
Summary: | Jenkins builds (source strategy) get intermittently stuck at the git-clone operation | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Christian Koep <ckoep> |
Component: | Build | Assignee: | Adam Kaplan <adam.kaplan> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | wewang <wewang> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.11.0 | CC: | adam.kaplan, antgarci, aos-bugs, bmilne, cmarches, dtarabor, gmontero, jdesousa, jokerman, ksalunkh, mmccomas, pweil, rbost, rhowe, rkrawitz, rphillips, sburke, wzheng, zhigwang |
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | stale | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-02-06 18:13:47 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
Christian Koep
2019-06-19 07:08:40 UTC
Customer is not able to exec or rsh into the pods: error: unable to upgrade connection: container not found ("docker-build") Reassigning to Adam, because there might be another issue with the git clone within the builder tool. Hi Adam, Have you had a chance to review the customer output Ben provided the other day? Issue summary (since the thread is very long): An OpenShift build with the `Binary` source strategy is initiated from a Jenkins pipeline. The build pod's `bsdtar` process appears to be hanging waiting for content to be uploaded. At present it is not clear why the build pod does not think the upload has completed - this requires further investigation. As an immediate work around, I recommend switching the Jenkins-initiated builds to clone source from a git-compatible repository (Github, Gitlab, Bitbucket, etc.) [1]. This kind of source strategy is more fault-tolerant than `Binary` source builds. Note that this work-around is not feasible for all situations. [1] https://docs.openshift.com/container-platform/3.11/dev_guide/builds/build_inputs.html#source-code |