Bug 848138 - Scaled apps are never restored once idle
Summary: Scaled apps are never restored once idle
Keywords:
Status: CLOSED DUPLICATE of bug 847920
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Ram Ranganathan
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-14 18:09 UTC by Bill DeCoste
Modified: 2015-05-15 02:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-14 19:04:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bill DeCoste 2012-08-14 18:09:14 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Bill DeCoste 2012-08-14 18:14:03 UTC
Description of problem:
When a scaled app goes idle, hitting the application from a browser does not restore the application. The result is the haproxt stats page only. An internal wget directly to the appl restores the app which then becomes accessible externally


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


How reproducible:


Steps to Reproduce:
1. Create a scaled jbossas-7
2. Wait until the application goes idle
3. Hit the application URL - this will show the haproxy stats page

4. ssh into the app
5. Issue a wget directly to the app
6. app will be restored and accessible externally
  
Actual results:
happroxy stats page, idle app


Expected results:
restored app accessible externally


Additional info:

Comment 2 Dan McPherson 2012-08-14 18:58:39 UTC
Is this a dup of:  847920

Comment 3 Bill DeCoste 2012-08-14 19:02:28 UTC
Ya, looks like it. Ram asked me to open a new bug and assign to him. I'll close this and comment on the other one.

Comment 4 Bill DeCoste 2012-08-14 19:04:22 UTC

*** This bug has been marked as a duplicate of bug 847920 ***


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