Description of problem: When navigating the GUI and attempting to lodge a Fedora Product bug the Bugzilla site appears to have locked up. Eventually the page is drawn correctly however this takes a significant amount of time. Although I have not been able to confirm myself using the wget function operates at the expected speeds. Version-Release number of selected component (if applicable): version 4.4.1012 How reproducible: Every time Steps to Reproduce: 1. Click New, 2. Select Fedora classification 3. Select Fedora Product 4. Wait Actual results: Very long load time. Expected results: Response in line with other products. Additional info:
I can reproduce this issue. The RH Bugzilla team is currently investigating.
John: When wgetting the page, did you have wget login to Bugzilla? If you wget without logging in, you'll get a quick response because Bugzilla will return an error page instead of the enter_bug form. You should view the .html file after wgetting it to ensure that it has the expected content.
*** Bug 1039636 has been marked as a duplicate of this bug. ***
I, and most (if not all) of my colleagues, can't create a new bugzilla report at all. We get HTTP 502 Proxy Error when we try to open a URL like this: https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora or this https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=anaconda We should be releasing Fedora 20 final version this week. We need Bugzilla operational, today. Can you please push the fix to production right now? Thanks!
(In reply to Kamil Páral from comment #6) > We should be releasing Fedora 20 final version this week. We need Bugzilla > operational, today. Can you please push the fix to production right now? > Thanks! This change will be released as part of Red Hat Bugzilla 4.4.1012-2 at 1am on Friday morning (UTC). -- simon
I just got in and was able to submit a new Fedora bug report. Whatever the problem is there must be some times when it does not happen.
Subject to verification of the fix on a staging system, we now plan a brief outage to deploy the fix at 00:00 UTC today. Obviously if the verification step reveals further issues we will need to reasses.
This change has now been deployed to the live server. -- simon
Thanks, I can now create new bugs without problems.
if i may be so kind, bugzilla.redhat.com is always slow. a few more hamsters for the wheel would be nice.
(In reply to customercare from comment #13) > if i may be so kind, bugzilla.redhat.com is always slow. a few more hamsters > for the wheel would be nice. New hamsters (aka servers) have been ordered, and should arrive in our data centre this week. It will still take a few months to rack up and performance test, but the (hamster?) wheels are definitely in motion for a significant hardware upgrade.