Bug 1435052 - CFME Performance of the Web has suddenly become bad.
Summary: CFME Performance of the Web has suddenly become bad.
Keywords:
Status: CLOSED DUPLICATE of bug 1435141
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: cfme-future
Assignee: Dan Clarizio
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-23 01:51 UTC by tachoi
Modified: 2020-05-14 15:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-08 13:54:51 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
trace log from evm.log (309.09 KB, text/plain)
2017-03-23 02:02 UTC, tachoi 		no flags Details
View All

Description tachoi 2017-03-23 01:51:16 UTC 
Description of problem:
- Performance of the CloudForms web ui has suddenly become bad. 
- Keep getting script timeout errors. No changes have been made to the system.
- CFME 5.7.0.17
- Below segmentation fault log entry found from UI node evm.log
=> Run `rails server -h` for more startup options
:/opt/rh/rh-ruby23/root/usr/share/gems/gems/puma-3.3.0/lib/puma/launcher.rb:89: [BUG] Segmentation fault at 0x000000000001c0
- no log entry found for "EVM Shutdown initiated"

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

How reproducible:
NA

Steps to Reproduce:
1.
2.
3.

Actual results:
UI is responding to service request becomes bad. 

Expected results:
UI is responding to service request with reasonable performance

Additional info:
Comment 3 tachoi 2017-03-23 02:02:49 UTC 
Created attachment 1265562 [details]
trace log from evm.log
Comment 7 Chris Kacerguis 2017-03-23 12:11:08 UTC 
This has been misfiled, and should be with the UI - Ops component.
Comment 8 Gregg Tanzillo 2017-03-23 21:49:30 UTC 
Please see https://bugzilla.redhat.com/show_bug.cgi?id=1435141#c6. The second paragraph explaining the cause for the UI to be unresponsive may be the same cause of this issue.
Comment 11 Dan Clarizio 2017-06-08 13:54:51 UTC 

*** This bug has been marked as a duplicate of bug 1435141 ***
Note You need to log in before you can comment on or make changes to this bug.