Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1384617 - Incorrect Webhook URL in the UI.
Incorrect Webhook URL in the UI.
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.3.0
All Linux
unspecified Severity high
: ---
: 3.3.1
Assigned To: Jakub Hadvig
Yadan Pei
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2016-10-13 12:55 EDT by Alfredo Quiroga
Modified: 2017-08-22 04:39 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously the URL for the webhook was assembled in a wrong way, where not the variable value for build config name and project name was used, but the the variable name itself was used. That was caused by incorrect 'editWebhookTriggers' directive's scope attribute type for the build config and project name. Now the issue is fixed and the variables values are used.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-10-27 11:43:06 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2084 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.3.1.3 bug fix update 2016-10-27 15:41:25 EDT

  None (edit)
Description Alfredo Quiroga 2016-10-13 12:55:58 EDT 
Description of problem:

Get the incorrect Webhook URL.

Version-Release number of selected component (if applicable):

Version

OpenShift Master:
v3.3.0.34
Kubernetes Master:
v1.3.0+52492b4

How reproducible:

Consistently

Steps to Reproduce:
1. In the web console, go to Builds -> Your-Build-Name -> Action -> Edit
2. Copy the webhook URL and put it in a document.
3. Now go to Builds -> Your-Build-Name -> Configuration
4. Copy the webhook URL and put it in a document.
5. Compare URLs.
6. When getting the URL via step 2, the URL is incorrect.

Actual results:


Expected results:


Additional info:
Comment 1 Jessica Forrester 2016-10-13 14:10:37 EDT 
@jhadvig the webhooks in the build config editor are incorrect.

Examples for comparison:

From editor: https://10.245.2.2:8443/oapi/v1/namespaces/project.metadata.name/buildconfigs/buildConfig.metadata.name/webhooks/6301dd92fa593571/github

From build configuration tab: https://10.245.2.2:8443/oapi/v1/namespaces/myproject/buildconfigs/php/webhooks/ed56abb1bd66ba76/generic

The one in the editor isn't getting the variables for project and build config name replaced.
Comment 2 openshift-github-bot 2016-10-13 16:11:11 EDT 
Commit pushed to master at https://github.com/openshift/origin-web-console

https://github.com/openshift/origin-web-console/commit/8311b12d7ce72ba78c6cf083cda9a2de6302d18b
Bug 1384617: Incorrect Webhook URL in the UI
Comment 4 Yadan Pei 2016-10-17 02:58:14 EDT 
Checked against v3.3.1.2

Webhook URL got from BC Configuration tab and BC Edit page are the same


When API port is set as 443, Webhook URL got from web console didn't contains the port number, just like https://<master>/oapi/v1/namespaces/yapei-manul-1/buildconfigs/php56/webhooks/e72f34f417f52839/github

When API port is set as 8443, Webhook URL got from web console contains the port number, just like https://<master>:8443/oapi/v1/namespaces/yapei-manul-1/buildconfigs/php56/webhooks/e72f34f417f52839/github

Move to VERIFIED
Comment 6 errata-xmlrpc 2016-10-27 11:43:06 EDT 
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-2016:2084
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.