Bug 962629 - Idled jbossews-2.0 apps will be stopped after migration from v1 to v2
Summary: Idled jbossews-2.0 apps will be stopped after migration from v1 to v2
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Paul Morie
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-14 05:35 UTC by joycezhang
Modified: 2015-05-14 23:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-11 03:57:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description joycezhang 2013-05-14 05:35:30 UTC
Description of problem:
If trying to idle an jbossews-2.0 app, then it would be stopped after migrating to v2 format.

Version-Release number of selected component (if applicable):
migrate from devenv_stage_351 to devenv_3223

How reproducible:
always

Steps to Reproduce:
1.Create a jbossews-2.0 app and idle it.
2.Migrate to devenv_3223 v2 env.
3.Check the app status
  
Actual results:
The app is stopped.
# rhc app show myews23 --state
Cartridge jbossews-2.0 is stopped.

Expected results:
It should still be idled:
# rhc app show myews23 --state
Cartridge jbossews-2.0 is idle

Additional info:

Comment 2 Rony Gong 🔥 2013-05-17 07:01:35 UTC
Verified on migration to devenv_3235
1. After migration, the jbossews-2.0 app is still in idle status

[root@ip-10-152-178-145 ~]# oo-idler -l
989479355045835161206784 is idled

2. Then access this jbossews-2.0 application, this app's status change to started.


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