Red Hat Bugzilla – Bug 1023305
Initial build app after creating app from quickstart does not restart the app if there's hot-deploy marker existing in the quickstart itself
Last modified: 2015-05-14 19:31:28 EDT
Description of problem:
Create app via https://github.com/matthicksj/scaling-demo, app can be created successfully, but meets 503 error when visiting the app.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create scaling demo app
rhc app-create scaleapp jbosseap mongodb-2 -s --from-code https://github.com/matthicksj/scaling-demo.git
2. Visit the app home page
Will met 503 error.
The app should work fine.
The demo app works well on current STG (devenv-stage_532),
And found the following error on both STG and devenv_3944,
2013/10/25 02:05:24,054 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014613: Operation ("read-resource") failed - address: ([("subsystem" => "deployment-scanner")]) - failure description: "JBAS014807: Management resource '[(\"subsystem\" => \"deployment-scanner\")]' not found"
The app is in start state after created but cannot be accessed.
# rhc app show scaleapp --state
Cartridge mongodb-2.2 is started
Cartridge jbosseap-6, haproxy-1.4 is started
After restart the app, the app can work well.
Low the severity.
Found that there is a hot_deploy marker for the scaling demo quickstart. That's way the app cannot be accessed after created but works well after restart.
Raise the severity.
Commit pushed to master at https://github.com/openshift/origin-server
Ignore hot_deploy for initial from-code build
Make sure local gear is started and in rotation when an initial build
git repository happens to have a hot deploy marker in it.
Checked the scale-demo on devenv_3953, the app can be accessed after created.
Move bug to verified.