Bug 967518 - Met "Reference ID" error when creating a jenkins server app if a jenkins server app already existed in domain
Summary: Met "Reference ID" error when creating a jenkins server app if a jenkins serv...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-27 10:39 UTC by joycezhang
Modified: 2015-05-15 00:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-11 04:11:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
fixed on INT (35.19 KB, image/png)
2013-05-29 02:39 UTC, joycezhang
no flags Details

Description joycezhang 2013-05-27 10:39:55 UTC
Description of problem:
If trying to create a jenkins server app in conditions of a jenkins server app existed, it would return error as below:

Unable to complete the requested operation due to: . Reference ID: 83d499f46ac34331f091c3d502cc15d5

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

How reproducible:
always

Steps to Reproduce:
1.Create an jenkins server app
2.Create another jenkins server app


Actual results:
Error is shown as pasted in description.

Expected results:
"Jenkins server app already existed" is shown instead of the Reference ID error.


Additional info:

Comment 1 Dan McPherson 2013-05-28 14:30:43 UTC
https://github.com/openshift/origin-server/pull/2650

Comment 3 joycezhang 2013-05-29 02:38:52 UTC
This issue is fixed on INT(devenv_3281), message "An application with jenkins-1.4 already exists within the domain. You can only have a single application with jenkins-1.4 within a domain."  is returned, please refer to attached screen shots.

Comment 4 joycezhang 2013-05-29 02:39:31 UTC
Created attachment 754117 [details]
fixed on INT


Note You need to log in before you can comment on or make changes to this bug.