Bug 811536

Summary:	Often get "execution expired" whille manipulating scalable apps
Product:	OKD	Reporter:	jizhao
Component:	Containers	Assignee:	Rob Millner <rmillner>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	medium
Version:	2.x	CC:	mfisher, szhou
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-13 23:43:51 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 jizhao 2012-04-11 11:07:00 UTC

Description of problem:
Often get "execution expired" while manipulating scalable apps, especially after adding several gears to it. Probably timeout.

Version-Release number of selected component (if applicable):
rhc-node-0.90.5-1.el6_2.x86_64
rubygem-stickshift-node-0.8.2-1.el6_2.noarch
rubygem-stickshift-controller-0.8.12-1.el6_2.noarch

How reproducible:
Often

Steps to Reproduce:
1.Create a scalable app
$ curl -k -H "Accept: application/xml" --user "jizhao+3:pas"  https://ec2-23-21-18-195.compute-1.amazonaws.com/broker/rest/domains/jizhao34/applications -X POST -d name=app1 -d cartridge=jbossas-7 -d scale=true
2.Scale it up
$ curl -k -H "Accept: application/xml" --user "<user>:<pass>"  https://<server_dns>/broker/rest/domains/<domain_name>/applications/<appname>/events -X POST -d event=scale-up
3.Embed mysql to it.
$ rhc app cartridge add -a <appname> -c mysql-5.1 -d
4.Destroy the app
  
Actual results:
Often get the following output on step3 and step4. Actually mysql is embedded successfully and app is destroyed successfully. Probably timeout.
<-------------------output------------------->
There was a problem communicating with the server. Response message: execution expired
If you were disconnected it is possible the operation finished without being able to report success.
You can use 'rhc domain show' and 'rhc app status' to learn about the status of your user and application(s).
<-------------------------------------------->

Expected results:
The client should be able to report the results.

Additional info:

Comment 1 Rob Millner 2012-06-19 23:41:52 UTC

I'm not able to reproduce this behaviour on devenv even after scaling up to 30 gears.  Was this on int or stg?

Comment 2 jizhao 2012-06-25 10:08:43 UTC

(In reply to comment #1)
> I'm not able to reproduce this behaviour on devenv even after scaling up to
> 30 gears.  Was this on int or stg?

It was on devenv. I've tested this bug on devenv_1893. It hardly happens now.
Changing the bug status to ON_QA.

Comment 3 jizhao 2012-06-26 02:38:57 UTC

According to comment 2, verify this bug.