Description of problem: If try to create a scalable app from a created quickstart in community with wordpress example, the app can't shown correctly in browser and all gears are down. Version-Release number of selected component (if applicable): devenv_2476 rhc-1.1.7.gem How reproducible: always Steps to Reproduce: 1.Enable quickstarts on instance. 2.Create a quickstart as Admin And add git repo url:https://github.com/openshift/wordpress-example.git 3.Add this quickstart to search index in drupal by hitting /community/cron.php. 4.Go to web console and create an scalable app with this quickstarts. 5.Check the app can work well. Actual results: App can not work correctly in Browser as attached sceenshot. Expected results: It works correctly. Additional info: 1.It can work well with non-scalable app with wordpress example. 2.It can work well for scalable app for the quickstart without initial git url added. 3.It can work well with the example with single cartridge, like https://github.com/openshift/flask-example.git
According to the comments from 876890, open this bug to track the wordpress example separately. Thanks.
This is a limitation in the quickstart itself. Do we want to limit this in the UI or warn in some way?
We can just alter the text in the quickstart description when we create it in the community (after sprint exit). It's not worth baking it into the core files because that could change if someone fixes it.
Assigning it back to quickstarts
Tested this issue on Stage(same package with devenv-stage_257), and found that not only wordpress app have the problem. Both wordpress, drupal, spring, capedwarf,JavaEE Full Profile Example on JBoss, have the same issue when creating scalable apps with these app types. However, cakephp, django, and ruby on rails app can work well both with scalable or non-scalable apps.
*** Bug 885266 has been marked as a duplicate of this bug. ***
Assigned. I am preparing a short-term fix that will suppress the scaling option for the known non-scalable quickstarts. This will not be a permanent fix; once the duct-tape solution is in place I will change this record to FutureFeature with some comments on a long-term solution.
The temporary fix is going into the stage build and also master. It specifically filters these known-non-scalable quickstarts by name, so it will not work for new quickstarts and it may accidentally mask similarly-named quickstarts that are actually scalable. Comments on the long term approach: Quickstart definitions are actually created in drupal, via a Quickstart-type drupal node template. A drupal-served API tells the console about them. So my proposal for the long-term is that we simply add a new boolean to the template that enables the creator to specify whether or not the quickstart is scalable. We can add the relevant info to the API and then consume it on a case-by-case basis in the console.
Created attachment 663412 [details] non_scalable_quickstart
Verified this bug on STG. Please refer to the details as below: 1. For the quickstarts that can support scalable apps(cakephp, django, and ruby on rails), they still work well when creating scalable apps with them. 2. For other quickstarts that can not support scalable apps, the scaling item is disabled when creating app. Please refer to the sceenshot as attached. Thanks.