Bug 1369702 - Cannot cancel openshift build when setting post-build in jenkins
Summary: Cannot cancel openshift build when setting post-build in jenkins
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ImageStreams
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Gabe Montero
QA Contact: Wang Haoran
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-24 07:56 UTC by wewang
Modified: 2017-03-08 18:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The OpenShift Pipeline Plugin for Jenkins did not properly handle permission issues when attempting to access the Route for Jenkins. Consequence: Any of the steps or post-build actions in Jenkins jobs could fail unnecessarily with a Java stack trace citing an inability to access routes. Fix: Add correct error handling when attempting to list routes. Result: Jenkins jobs not longer fail unnecessarily if the token used by the OpenShift Pipeline Plugin for Jenkins to access the OpenShift API Master did not have permission to list routes.
Clone Of:
Environment:
Last Closed: 2016-09-27 09:10:33 UTC
Target Upstream Version:

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1937 0 normal SHIPPED_LIVE Red Hat OpenShift Enterprise Jenkins image bug fix and enhancement update 2016-09-27 13:05:12 UTC

Comment 1 wewang 2016-08-24 08:01:36 UTC 
"Cancel openshift deployment" has the same problem, plugin updated before,  features are always works.
Comment 2 wewang 2016-08-24 08:12:54 UTC 
Can you check build step and post-build actions, because when tested "Create resources in OpenShift" also report "com.openshift.restclient.authorization.ResourceForbiddenException"
Comment 3 Gabe Montero 2016-08-24 16:53:40 UTC 

*** This bug has been marked as a duplicate of bug 1369746 ***
Comment 5 wewang 2016-08-31 10:23:44 UTC 
I think the bug's reason is serviceacount changed to jenkins,will verified it later
Comment 6 Gabe Montero 2016-08-31 14:13:44 UTC 
@wewang - if you do still see problems after accounting for the change in service account, please include the latest stack trace and confirm the plugin version, as they should be different from what you posted in the original description.
Comment 7 wewang 2016-09-01 03:13:58 UTC 
when use serviceaccount:jenkins , it  works
Comment 9 errata-xmlrpc 2016-09-27 09:10:33 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/RHBA-2016:1937
Note You need to log in before you can comment on or make changes to this bug.