Bug 808656

Summary:	existing stopped app on stage becomes to idle
Product:	OKD	Reporter:	Meng Bo <bmeng>
Component:	Pod	Assignee:	Jhon Honce <jhonce>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	high
Version:	1.x	CC:	dmcphers, jialiu, mpatel, rmillner
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-27 20:45:46 UTC	Type:	---
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 2012-03-31 03:31:05 UTC

Description of problem:
stopped apps on old instance will change to idle status after upgrade and migration.

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

How reproducible:
always

Steps to Reproduce:
1.create some apps on old stage 
2.change the app status to 'stop'
3.after server upgrade and migration check if the app available.
  
Actual results:
the app becomes to idle status after server upgrade and migration.

Expected results:
the app should keep stop status.

Additional info:

Comment 1 Johnny Liu 2012-03-31 05:16:14 UTC

I also encounter this issue.  Maybe the above step is not enough to reproduce this issue, I clarify it more clear.

I have a stopped app on stage that is created a long time ago (maybe several sprint ago). Today, I try to access it, I find that my stopped app becomes "idled", after access my app url, the app wakes up from "idled" status.

Will stopped app also be "idled" on stage after no access for a long time?

Comment 2 Meng Bo 2012-03-31 06:02:37 UTC

this issue cannot be recreated on devenv migrate operation.
it only happens on stage environment.

Comment 3 Johnny Liu 2012-03-31 12:00:02 UTC

(In reply to comment #2)
> this issue cannot be recreated on devenv migrate operation.
> it only happens on stage environment.

Ignore this comments, because I can find a way to reproduce it.

After stop app, idle it again manually, this app wil be waked up by accessing app url.

Do some more dig, I found rhc-autoidler, found it will check all application, even already stopped app. So I think the root cause is that rhc-autoidler miss a filter to exclude already stopped apps.

Comment 4 Johnny Liu 2012-03-31 12:11:07 UTC

rhc-autoidler is never run in devenv.

Comment 5 Johnny Liu 2012-04-01 08:55:14 UTC

I think it is better to give a fix patch to rhc-idler. Because stopped app should NOT be "idled". When trying to idle a "stopped" app, should skip it, and this seems to make more sense.

Comment 6 Jhon Honce 2012-04-18 17:36:34 UTC

fixed in commit 10797174f2686396ea75c8bc687ee21ac8112c04

Comment 7 Johnny Liu 2012-04-19 03:35:06 UTC

This patch introduce a new issue, rhc-idler does NOT any more, I will open another bug (Bug 814024) to track it. After Bug 814024 is fixed, I will verify this bug.

Comment 8 Meng Bo 2012-04-20 04:56:49 UTC

checked on devenv_1732, issue has been fixed.
rhc-idler will not handle the stop status apps.