Bug 1373441
| Summary: | New build by webhook url started without any output info | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | XiaochuanWang <xiaocwan> |
| Component: | Build | Assignee: | Ryan Murphy <rymurphy> |
| Status: | CLOSED ERRATA | QA Contact: | XiaochuanWang <xiaocwan> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | aos-bugs, bparees, dyan, ffranz, jokerman, mmccomas, tdawson |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: When a build is started from a webhook, the server response does not contain a body
Consequence: The CLI cannot easily determine the generation of the created build, and cannot report it to the user
Fix: Change webhook response to contain the created Build object in the body
Result: The CLI can now report the correct build generation when created.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-10 05:15: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: | |||
|
Comment 1
Ryan Murphy
2017-01-19 22:39:19 UTC
PR Mentioned above has been merged, marking ON_QA This has been merged into ocp and is in OCP v3.6.27 or newer. Verified on v3.6.27 # oc start-build --from-webhook="https://host-xxx.rdu2.redhat.com:8443/oapi/v1/namespaces/xiaocwan-b/buildconfigs/ruby-sample-build/webhooks/secret101/generic" 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/RHEA-2017:1716 |