Bug 1022982

Summary: Added gear is always 'DOWN' for jboss scalable app
Product: OpenShift Online Reporter: Lei Zhang <lzhang>
Component: ContainersAssignee: Andy Goldstein <agoldste>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.xCC: xtian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-24 03:26:31 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 Lei Zhang 2013-10-24 11:55:49 UTC
Description of problem:
Create jbossews-1.0 scalable app(e.g.,myjbossews10s), scale up app via REST API,
check the page of haproxy-status, access the created gear.Found the created gear is always DOWN

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

How reproducible:
always

Steps to Reproduce:
1.Create one jboss(jbossas-7,jbosseap-6,jbossews-1.0 or jbossews-2.0) scalable app
rhc app create myjbossas7s jbossas-7 -s
2.Scale up via REST API
curl -k -H "Accept:application/xml" --user "chunchen:redhat7" https://ec2-54-211-118-92.compute-1.amazonaws.com/broker/rest/domains/chunchen/applications/myjbossas7s/events -d event=scale-up -X POST

[lijun@ray Work]$ rhc app show --gear -a myjbossas7s
ID                               State   Cartridges            Size  SSH URL
-------------------------------- ------- --------------------- ----- ------------------------------------------------------------------------------------------
52690600a6f4338ac30008a0         started jbossas-7 haproxy-1.4 small 52690600a6f4338ac30008a0.rhcloud.com
930244503ca011e3996b22000a8a091d started jbossas-7 haproxy-1.4 small 930244503ca011e3996b22000a8a091d.rhcloud.com

3.Access the added app via browser
930244503ca011e3996b22000a8a091d-chunchen.dev.rhcloud.com
http://myjbossas7s-chunchen.dev.rhcloud.com/haproxy-status

Actual results:
No content display when access the added gear via browser, found added gear always DOWN from the page of 'haproxy-status'

Expected results:
Added gear can be accessed after scale up

Additional info:

Comment 1 Andy Goldstein 2013-10-24 20:14:22 UTC
https://github.com/openshift/origin-server/pull/3985

Comment 2 openshift-github-bot 2013-10-24 21:28:38 UTC
Commit pushed to master at https://github.com/openshift/origin-server

https://github.com/openshift/origin-server/commit/92ce8db82408c0b27596d304c3cb7ba26fa31bc9
Bug 1022982

Only rsync from repo to JBoss cartridge webapps/deployments directory
if the repo directory has files in it.

Don't delete content from the cartridge dir unnecessarily.

Comment 3 Lei Zhang 2013-10-25 02:25:52 UTC
devenv_3942, still can reproduce this issue. 

1.After scale up jbossas-7 scalable app, check added gear via browser, found no content displays
[rayzhang@ray Work]$ curl http://162579420888190377000960-chunchen.dev.rhcloud.com/
[rayzhang@ray Work]$ 


2. Check the status from 'haproxy-status', added gear is always 'DOWN'
http://myjbossas7s-chunchen.dev.rhcloud.com/haproxy-status

Comment 4 Xiaoli Tian 2013-10-25 03:15:41 UTC
Move it back to ON_QA to re-test until the fixed in version devenv_3944 ready for testing.

Comment 5 Lei Zhang 2013-10-25 06:01:36 UTC
devenv_3944, This bug has been fixed.After scale up, added gear can be accessed and the status of added gear is 'Started' in the 'haproxy-status' page.

[rayzhang@ray Work]$ curl -I http://6f3da3a83d3a11e3943d22000aef0946-chunchen.dev.rhcloud.com/
HTTP/1.0 200 OK
Date: Fri, 25 Oct 2013 06:01:04 GMT
Server: Apache-Coyote/1.1
Accept-Ranges: bytes
ETag: W/"6760-1382680727000"
Last-Modified: Fri, 25 Oct 2013 05:58:47 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 6760
Vary: Accept-Encoding,User-Agent
ProxyTime: D=3698
X-Cache: MISS from file01.intranet.prod.int.rdu2.redhat.com
X-Cache-Lookup: MISS from file01.intranet.prod.int.rdu2.redhat.com:8080
Via: 1.0 file01.intranet.prod.int.rdu2.redhat.com (squid/3.1.10)
Connection: keep-alive