Bug 1312826

Summary: [devexp_public_640] Failed to "Cancel deployments in Openshift" via jenkins
Product: OpenShift Container Platform Reporter: wewang <wewang>
Component: ImageStreamsAssignee: Gabe Montero <gmontero>
Status: CLOSED ERRATA QA Contact: Wang Haoran <haowang>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2.0CC: aos-bugs, bparees, gmontero, haowang, jokerman, mmccomas, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1292021 Environment:
Last Closed: 2016-05-12 16:30:39 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: 1292021    
Bug Blocks: 1294940, 1308390    

Comment 3 Gabe Montero 2016-02-29 15:11:05 UTC 
With the cannot trigger pod item from Comment #1 was https://github.com/openshift/origin/issues/7663, whose fix just got merged into origin a few minutes ago.

With the exception on the cancel deployments, at least with what was pasted in bugzilla, there appears to be a space prior to the "wewang".  If that is fact correct, I suspect a space was entered in the project name field prior to "wewang".

Please confirm / retry, insuring that there is no space.  Return the bugzilla back to me either way with the results.

If this was the case, moving forward, the plugin code could certainly trim any preceding / succeeding spaces (an old UI gotcha that slipped my mind).

If this is not the case, and it is reproducible, we'll need to start debugging the plugin dependency openshift-restclient-java, which actually makes the REST api call.
Comment 4 wewang 2016-03-02 02:26:16 UTC 
@Gabe Montero, sorry about cancel deployment, my mistake, it works

and use template to create jenkins directly, it also works now, thx
Comment 6 errata-xmlrpc 2016-05-12 16:30:39 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/RHSA-2016:1064