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:
I'm not able to reproduce this behaviour on devenv even after scaling up to 30 gears. Was this on int or stg?
(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.
According to comment 2, verify this bug.