Bug 1373441 - New build by webhook url started without any output info
Summary: New build by webhook url started without any output info
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Ryan Murphy
QA Contact: XiaochuanWang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-06 09:47 UTC by XiaochuanWang
Modified: 2017-08-16 19:51 UTC (History)
7 users (show)

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.
Clone Of:
Environment:
Last Closed: 2017-08-10 05:15:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1716 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 09:02:50 UTC

Comment 1 Ryan Murphy 2017-01-19 22:39:19 UTC 
Opened a fix here: https://github.com/openshift/origin/pull/12573
Comment 2 Ryan Murphy 2017-03-18 19:05:36 UTC 
PR Mentioned above has been merged, marking ON_QA
Comment 3 Troy Dawson 2017-04-11 21:04:28 UTC 
This has been merged into ocp and is in OCP v3.6.27 or newer.
Comment 5 XiaochuanWang 2017-04-13 06:19:26 UTC 
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
Comment 7 errata-xmlrpc 2017-08-10 05:15:47 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.