Bug 1021836 - Zend apps become inaccessible(error 500) after several builds with hot_deploy marker
Summary: Zend apps become inaccessible(error 500) after several builds with hot_deploy...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Andy Goldstein
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-22 08:03 UTC by Zhe Wang
Modified: 2015-05-14 23:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-24 03:26:03 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Zhe Wang 2013-10-22 08:03:30 UTC
Description of problem:
Given a Zend app with hot_deploy marker added, after several builds (usually two rounds of builds), the app becomes inaccessible, returnning 500 error when checking the HTTP status.

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

How reproducible:
always

Steps to Reproduce:
1. create a zend app
2. create a hot_deploy marker and trigger a build
3. check the availability of the app's homepage
4. make another change and trigger a second build
5. check the availability of the app again
6. repeat Step 4 and 5 several times

Actual results:
The app was accessible in Step 3, but in Step 5 its homepage became blank, returning error 500 when checking the header of the response.

Expected results:
The zend app should be always accessible after several builds with hot_deploy marker.


Additional info:

Comment 1 Dan Mace 2013-10-23 14:49:11 UTC
Seems to be resolved as of devenv_3934.

Comment 2 Zhe Wang 2013-10-24 08:34:27 UTC
Verified in devenv_3837.


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