Bug 789885

Summary: Time out problem occurs when creating an application on express console page.
Product: OKD Reporter: Yujie Zhang <yujzhang>
Component: PodAssignee: Krishna Raman <kraman>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: high Docs Contact:
Priority: medium    
Version: 2.xCC: aboone, mfisher, szhou, 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: 2012-02-17 02:07:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Time out problem. none

Description Yujie Zhang 2012-02-13 07:40:39 UTC
Created attachment 561432 [details]
Time out problem.

Description of problem:

Time out problem occurs when creating an application on express console page.

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

rhc-site-0.86.1-1.git.341.d96e1be.el6.noarch

How reproducible:always


Steps to Reproduce:
1.Go to Openshift website and log in 
2.Go to express console
3.Try to create an new application
  
Actual results:

The application is created but time out problem occured with the following message:

"We're sorry, this operation has timed out. It is possible that it was successfully completed, but we are unable to verify it. " 

Details see in attachment.

Expected results:

The application should be created successfully without time out problem.

Additional info:

Comment 1 Yujie Zhang 2012-02-13 07:58:51 UTC
This issue happened when I use the streamline-aws.rb.

Comment 2 Alex Boone 2012-02-14 20:51:18 UTC
For one app creation attempt from the web site, I saw 11 of these lines in the broker log:

DEBUG: rpc_client.custom_request('cartridge_do', {:action=>"cartridge-list", :cartridge=>"cloud-sdk-node", :args=>"--porcelain --with-descriptors"}, domU-12-31-39-0A-94-32, {'identity' => domU-12-31-39-0A-94-32})

I suspect that the number of lists is tolerable w/o Streamline involved but Streamline pushes this over the timeout window.  Anything that can be done to reduce the number of cartridge list requests that are being performed?

Comment 3 Krishna Raman 2012-02-15 17:03:26 UTC
Turned on caching of cartridges in the streamline-aws profile.
Dan improved the speed of finding nodes for the cartridge cache.

Comment 4 Yujie Zhang 2012-02-16 05:25:47 UTC
(In reply to comment #3)
Verify this bug on rhc-site-0.86.8-1.el6_2.noarch,it's fixed now.