Bug 893877 - [fork][model refactor]cannot stop non-scalable jbossews-2.0 app
Summary: [fork][model refactor]cannot stop non-scalable jbossews-2.0 app
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-10 05:28 UTC by Zhe Wang
Modified: 2015-05-15 02:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 23:46:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Zhe Wang 2013-01-10 05:28:25 UTC
Description of problem:
failed to stop a non-scalable jbossews-2.0 app


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


How reproducible:
always

Steps to Reproduce:
1. create a non-scalable jbossews-2.0 app
$ rhc app create jbsews jbossews-2.0
2. stop this app
$ rhc app stop jbsews
3. visit the link of this app
http://jbsews-fork395.dev.rhcloud.com/
4. show the status of the metrics-0.1 cartridge
$ rhc cartridge status metrics-0.1 -a jbsews
  
Actual results:
in step 3, the link is accessible

result in steup 4:
RESULT:
Total Accesses: 8634
Total kBytes: 429
CPULoad: 2.4358
Uptime: 1106
ReqPerSec: 7.80651
BytesPerSec: 397.193
BytesPerReq: 50.8798
BusyWorkers: 1
IdleWorkers: 1
Scoreboard: W..._

Expected results:
the jbossews-2.0 app should be stopped successfully

Additional info:

Comment 1 Zhe Wang 2013-01-10 10:14:13 UTC
(In reply to comment #0)
> 4. show the status of the metrics-0.1 cartridge
> $ rhc cartridge status metrics-0.1 -a jbsews

sorry, this step should be
4. show the status of the app
$ rhc app show --state jbsews

and in this step, the result was

RESULT:
Gear group jbossews-2.0 is started

Comment 2 Dan McPherson 2013-01-11 02:40:05 UTC
This is an upstream problem.  ews-2.0 is not being built and installed because it's in the ignore packages packages list.  So it's just installing the published rpm everytime rather than the one from the fork.

Comment 3 Dan McPherson 2013-01-17 14:51:04 UTC
Can you try this again now.  The updated package is now included in the fork ami.

>= fork_ami_refctr1_420

Comment 4 Chandrika Gole 2013-01-17 19:01:26 UTC
Tested this on fork_ami_refctr1_420


Note You need to log in before you can comment on or make changes to this bug.