Bug 1021836

Summary:	Zend apps become inaccessible(error 500) after several builds with hot_deploy marker
Product:	OpenShift Online	Reporter:	Zhe Wang <zhewang>
Component:	Containers	Assignee:	Andy Goldstein <agoldste>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.x	CC:	dmace, xtian
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:	2014-01-24 03:26:03 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 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.