Bug 1023305

Summary: Initial build app after creating app from quickstart does not restart the app if there's hot-deploy marker existing in the quickstart itself
Product: OpenShift Online Reporter: Meng Bo <bmeng>
Component: ContainersAssignee: Andy Goldstein <agoldste>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: agoldste, jhonce
Target Milestone: ---Keywords: Regression
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:26:43 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:

Description Meng Bo 2013-10-25 07:23:01 UTC
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):
devenv_3944

How reproducible:
Always

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
3.

Actual results:
Will met 503 error.

Expected results:
The app should work fine.

Additional info:
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"

Comment 1 Meng Bo 2013-10-25 07:51:50 UTC
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.

Comment 2 Meng Bo 2013-10-25 08:11:44 UTC
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.

Comment 3 Andy Goldstein 2013-10-25 12:58:26 UTC
https://github.com/openshift/origin-server/pull/3992

Comment 4 openshift-github-bot 2013-10-25 15:34:03 UTC
Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/f754d2f570fd66596b9cb66bed9dada01a5351c4
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.

Bug 1023305

Comment 5 Meng Bo 2013-10-28 05:23:47 UTC
Checked the scale-demo on devenv_3953, the app can be accessed after created.

Move bug to verified.