Bug 1560661
| Summary: | Binary build with --from-file not working | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ben Parees <bparees> |
| Component: | Build | Assignee: | Ben Parees <bparees> |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.10.0 | CC: | aos-bugs, vwalek, wzheng |
| Target Milestone: | --- | ||
| Target Release: | 3.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Build pods use multiple containers. Binary builds need to specify which container to stream content into, and for custom builds the name of the container is different from non-custom builds.
Consequence: When streaming binary content into a custom build, the expected container (git-clone) does not exist and the build fails.
Fix: The logic for streaming binary content into a custom build pod will be changed to reference the correct container name (custom-build)
Result: Binary content will successfully stream into the custom build container.
|
Story Points: | --- |
| Clone Of: | 1560608 | Environment: | |
| Last Closed: | 2018-07-30 19:11:31 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: | |||
| Bug Depends On: | 1560608 | ||
| Bug Blocks: | 1560659 | ||
|
Comment 1
Ben Parees
2018-03-26 17:53:04 UTC
Commit pushed to master at https://github.com/openshift/origin https://github.com/openshift/origin/commit/1753e9c03fdf5507bf815b0b198588915fa7f389 setup binary input for custom builds properly bug 1560661 https://bugzilla.redhat.com/show_bug.cgi?id=1560661 Verified with below steps on v3.10.0-0.22.0: 1. Edit custom builder image Dockerfile like below: #CMD ["/tmp/build.sh"] ENTRYPOINT tar -xf - 2. docker build . -t custom-builder 3. Create a custom build with above customized builder image 4. git clone https://github.com/openshift/ruby-hello-world; tar -cf ruby-hello-world.tar.gz ruby-hello-world 5. $ oc start-build ruby-sample-build --from-file=ruby-hello-world.tar.gz --follow --wait --loglevel=5 Uploading file "ruby-hello-world.tar.gz" as binary input for the build ... build "ruby-sample-build-2" started 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-2018:1816 |