Bug 798059 - Scaling an app fails on Proxy Error.
Summary: Scaling an app fails on Proxy Error.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Rajat Chopra
QA Contact: Chandrika Gole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-27 23:29 UTC by Chandrika Gole
Modified: 2015-05-15 01:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-28 19:39:13 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Chandrika Gole 2012-02-27 23:29:02 UTC
Description of problem:
As per US1463 I should be able to scale up an app, but I am not able to scale up the app. 

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

How reproducible:
Always

Steps to Reproduce:
1. Create a scaleable app -
curl -k -H "Accept: application/xml" --user "<user>:<pass>"  https://localhost/broker/rest/domains/<user>/applications -X POST -d name=<appname> -d cartridge=php-5.3 -d scale=true
2. Scale up the app -
curl -k -H "Accept: application/xml" --user "<user>:<pass>"  https://localhost/broker/rest/domains/<user>/applications/<appname>/events -X POST -d event=scale-up
3.
  
Actual results:
Scale up fails -

<title>502 Proxy Error</title>
</head><body>
<h1>Proxy Error</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
The proxy server could not handle the request <em><a href="/broker/rest/domains/cgole10/applications/p1/events">POST&nbsp;/broker/rest/domains/cgole10/applications/p1/events</a></em>.<p>
Reason: <strong>Error reading from remote server</strong></p></p>
<hr>

Expected results:
App should scale up.

Additional info:

Comment 1 Chandrika Gole 2012-02-27 23:31:40 UTC
Had a discussion with Rajat, and he figured this is an mcollective issue.  Still debugging the issue..

Comment 2 Rajat Chopra 2012-02-28 03:13:23 UTC
The mcollective on this build suspiciously takes long. The request times out from passenger proxy. The mcollective calls to some hooks sometimes take a minute. Total request time being ~200 seconds. Thats a lot.

Tested this with new build - cant reproduce the problem. The total request time on new build is ~40 seconds. Scale up times are ~25 seconds.

The request for scaling is heavy and needs to be looked into in the future anyway, though.

Comment 3 Chandrika Gole 2012-02-28 19:39:13 UTC
THis bug was filed against a micro instance. Scaling up and down works fine on a large instance.


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