Bug 973388 - Route clashes prevent viewing application named "new"
Summary: Route clashes prevent viewing application named "new"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Jessica Forrester
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-11 20:29 UTC by Jessica Forrester
Modified: 2015-05-15 01:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-24 14:53:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jessica Forrester 2013-06-11 20:29:00 UTC
Description of problem:
An application named "new" can be created but then the application /applications/<app name> page will go to /applications/new which redirects to the page for creating a new application.

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


How reproducible:
Reproducible in all environments.

Steps to Reproduce:
1. Create a new application named "new"
2. Go to the application's information page

Actual results:
Redirected to page to create a new application

Expected results:
Shows the "new" application's information (cartridges, aliases, etc)

Additional info:
This is part of a larger issue around routes clashing, to resolve this issue all plural URL paths will become singular in the website and new APIs will be exposed in the broker that allow use of singular paths. All old plural broker APIs will remain for now.

ex: /applications/<app-name> in the website will now be accessed as /application/<app-name>

Comment 1 Jessica Forrester 2013-06-11 20:29:51 UTC
Fixes are in https://ci.dev.openshift.redhat.com/jenkins/job/fork_ami/656/

Comment 2 Yujie Zhang 2013-06-13 05:39:53 UTC
Tested on fork_ami_openshift_656, the application details page of app named "new" can be accessed successfully, so verify this bug, thanks.


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