Bug 1019526

Summary:	got incomplete html response when the server returns a http 504 in PROD.
Product:	OpenShift Online	Reporter:	Peter Ruan <pruan>
Component:	Master	Assignee:	Lili Nader <lnader>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.x	CC:	mfisher, zzhao
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:	2013-10-17 13:35:54 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 Peter Ruan 2013-10-16 00:38:04 UTC

Description of problem:
  When trying to scale up a php app in PROD, it timed out, but the response from the server is incomplete.


DEBUG:    code 200  597 ms
This operation will run until the application is at the minimum scale and may take several minutes.
Setting scale range for php-5.3 ... DEBUG: Setting scales = scales_from: 2
DEBUG: Using token authentication
DEBUG: Request PUT https://openshift.redhat.com/broker/rest/domain/op0sd1/application/app5/cartridge/php-5.3
DEBUG:    code 504 300130 ms
DEBUG: Response did not include a message from server: invalid character at "<html><bod"
Server returned an unexpected error code: 504


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

How reproducible:
always.

Steps to Reproduce:
1. rhc app create app4 php-5.3 -s 
2. rhc cartridge  scale php-5.3 -a app5 --min 2 -d
3.

Actual results:
Response did not include a message from server: invalid character at "<html><bod"

Expected results:
a valid html repsonse

Additional info:

Comment 1 Lili Nader 2013-10-16 06:24:12 UTC

A 504 is a gateway timeout error.  See more info here
http://pcsupport.about.com/od/findbyerrormessage/a/504error.htm

Most likely what has happened is that the proxy server timeout waiting for the broker to respond from the scale-up event.  The response most likely truncated by the rhc client tools (meaning not shown is full) is most probably from the proxy server.

Possible fixes 

- increase timeout on proxy server
- speed up scaling.

Comment 2 zhaozhanqi 2013-10-17 12:14:27 UTC

 According to comment 1,This bug is caused by gateway timeout, we can avoid it by increase timeout. so change to verified temporary.