Bug 1020436

Summary: Dashboard not working for existing app
Product: OpenShift Online Reporter: Kris Kong <kris>
Component: WebsiteAssignee: Clayton Coleman <ccoleman>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 2.xCC: jliggitt, kris, yujzhang
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-24 03:24:56 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:

Description Kris Kong 2013-10-17 16:18:45 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Login to Openshift Dashboard
1. Click on the Gear Icon of any existing app created before the new Dashboard was implemented.
2. Redirected to an error page. https://openshift.redhat.com/app/console/application/518206594382ecc0e000001b-dev

Actual results:
https://openshift.redhat.com/app/console/application/518206594382ecc0e000001b-dev

Expected results:
Dashboard

Additional info:
Comment 1 Yujie Zhang 2013-10-18 02:12:09 UTC 
Can you specify the error message? We can not access your app details page, thanks.
Comment 2 Jordan Liggitt 2013-10-18 18:48:46 UTC 
Do you have a reference id from the error page?
Comment 3 Jordan Liggitt 2013-10-18 18:53:24 UTC 
This may be related to a known issue. What web cartridge was part of the application, and do you know if it was scalable?
Comment 4 Kris Kong 2013-10-19 05:32:08 UTC 
The error can be view on the following link:
https://openshift.redhat.com/app/console/application/518bc16f5973ca8646000075-realtywall?__utma=222392261.1921254616.1382160321.1382160321.1382160321.1&__utmb=222392261.10.10.1382160321&__utmc=222392261&__utmx=-&__utmz=222392261.1382160321.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)&__utmv=-&__utmk=82014101

I've posted it on the forum previously.

I was using a PHP cartridge (installed with MySQL) that is scalable.
Comment 5 Yujie Zhang 2013-10-21 07:01:18 UTC 
Tested on STG(devenv-stage_521), console can work correctly for the old existing scalable application, will verify this bug once it is on qa, thanks.
Comment 6 Yujie Zhang 2013-10-23 02:17:50 UTC 
Tested on STG(devenv-stage_528), verify this bug since console can work correctly for the old existing scalable application, thanks.