Bug 847917 - The scalable app home page can't get back by hit app page if app is idled
Summary: The scalable app home page can't get back by hit app page if app is idled
Keywords:
Status: CLOSED DUPLICATE of bug 847920
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-14 02:28 UTC by Rony Gong 🔥
Modified: 2015-05-15 02:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-14 02:53:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
/var/log/httpd/access_log (3.31 KB, text/plain)
2012-08-14 02:32 UTC, Rony Gong 🔥
no flags Details

Description Rony Gong 🔥 2012-08-14 02:28:32 UTC
Description of problem:
The scalable app home page can't get back by hit app page if app is idled
like access: http://qsphp-qgong5.dev.rhcloud.com/

but could get back by access app gear page. like:
http://7c806abb41-qgong5.dev.rhcloud.com/

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


How reproducible:
always

Steps to Reproduce:
1.Create an scalable app
2.After a period of time(this will make app idler), then hit the app home page
3.
  
Actual results:
only show haproxy status


Expected results:
the app statue should become started, and hit the app home page, the app page should come back.

Additional info:
Since the idler mechanism is caused by 2 condition, one is check the commit time, another is check the access time in /var/log/httpd/access_log

And I could find the app gear(7c806abb41-qgong5) access log in above log after I just created a scalable app. so it will cause  both app gear and haproxy gear  idler.

Comment 1 Rony Gong 🔥 2012-08-14 02:32:16 UTC
Created attachment 604131 [details]
/var/log/httpd/access_log

Comment 2 Rony Gong 🔥 2012-08-14 02:53:13 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.