Bug 1000032

Summary:	RedHat Bugzilla instance does not allow me to consult "My bugs"
Product:	[Community] Bugzilla	Reporter:	Sergio Freire <sergio-s-freire>
Component:	User Interface	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	jmcdonal, rjoost
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:	2013-08-27 23:06:53 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 Sergio Freire 2013-08-22 14:15:55 UTC

Description of problem:
"My bugs" page does not open; it gives timeout.

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

How reproducible:
Always

Steps to Reproduce:
1. Login with my credentials
2. Choose "My bugs" 

Actual results:
The webpage does not open; it gives timeout.

Expected results:
I should bugs reported by me.

Additional info:

Comment 1 Jason McDonald 2013-08-22 23:24:03 UTC

Seems to be working for me. "My Bugs" takes about 12 seconds to show me a little over 400 bugs.  Rerunning the same query with your email address takes about 5 seconds to show me a list of 4 bugs (including this one).

Can you still see the timeouts? It's possible that the system was heavily loaded yesterday due to some users' excitement about Bugzilla reaching Bug 1000000.

Comment 2 Sergio Freire 2013-08-23 10:40:59 UTC

Yes, the timeout remains. I have seen this in the past but I just ignored it at that the time. The problem remains. Im authenticated with my user and just the "My bugs" option gives timeout. 
Due to your feedback, I experimented Chrome and IE 10.
The timeout only happens with Chrome (it tries to open and about 20 seconds after it, which is strange.

In IE10.. after 5 seconds it gives my bugs.

Comment 3 Jason McDonald 2013-08-26 03:21:18 UTC

I just tried it using Chrome Version 29.0.1547.57 on Fedora 19 and didn't get any timeouts.

Are you using the stable version of Chrome? Which host operating system? Do you have any Chrome extensions installed?  It would be good if you could test a clean install of Chrome without any extensions.

Comment 4 Sergio Freire 2013-08-27 08:21:04 UTC

yes im using the latest stable. im on windows. now suddenly it works ok..!? the only thing different from the past is that i updated chrome from 28 to 29 but... it may be just a coincidence. well, i cannot reproduce it anymore. i guess it was not an overload because it worked in ie and not in chrome.