Red Hat Bugzilla – Bug 621030
Fail to save traceback to bugzilla
Last modified: 2010-08-05 13:53:21 EDT
Created attachment 436425 [details]
Files under tmp
Description of problem:
I encountered an exception in anaconda and tried to save it to bugzilla. But after I input the name and passwd. I got no response (waiting about 10mins).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install 14-Alpha-TC2 directly until an exception occurred
2. Save traceback to bugzilla
No response, and I think the bug isn't filed as well.
bug filed with a feedback.
Created attachment 436793 [details]
UI after reporting to bugzilla
Confirmed. After attempting to report to bugzilla UI stays completely blank with Next and Back buttons. Next doesn't work, Back does (but you can't continue installation anyway).
Created attachment 436795 [details]
When switching to console, I found an error that could have caused this. Only a few last lines are visible, mainly:
AttributeError: HTTPSConnection instance has no attribute 'getreply'
Created attachment 436796 [details]
My logs from installation, I can't find that console traceback there.
Blocking F14Alpha according to F14 Alpha Release Criteria.
I believe this should be reported against anaconda (package 'report' is not even installed), changing.
report doesn't need to be installed. It's on the installation images and is used by anaconda to do the reporting. Please don't second guess me like that - I do know what I'm talking about.
Having gotten a little more information, though, I believe this is the python-bugzilla traceback I've been seeing elsewhere.
(In reply to comment #6)
> report doesn't need to be installed. It's on the installation images and is
> used by anaconda to do the reporting. Please don't second guess me like that -
> I do know what I'm talking about.
There was no comment from you and it didn't occur to me to examine bug history, so I thought it had been reported originally against report by He Rui. Now I see it was reported against anaconda and you changed it to report just after that. So, sorry for that, it wasn't intentional.
What are the next steps and plans for fixing this bug? Can someone please provide more inofrmation?
If this is in fact a blocker we can't compose the Fedora 14 Alpha Release Candidate today unless it is fixed.
*** This bug has been marked as a duplicate of bug 621298 ***