Bug 848138

Summary: Scaled apps are never restored once idle
Product: OKD Reporter: Bill DeCoste <wdecoste>
Component: PodAssignee: Ram Ranganathan <ramr>
Status: CLOSED DUPLICATE QA Contact: libra bugs <libra-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.xCC: dmcphers, mfisher
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-14 19:04:22 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:
Embargoed:

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 ***