Bug 519016

Summary: trying to save stack trace to bugzilla during install fails
Product: [Fedora] Fedora Reporter: Don Zickus <dzickus>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-24 17:37:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Don Zickus 2009-08-24 15:43:01 UTC 
Description of problem:
So my attempt to upgrade from F10 to rawhide failed.  I tried to be lazy and use the save to bugzilla option.  I entered my username/password and a short description.  After clicking on OK, my attempt seemed to fail with a -3, I think.

There wasn't much to save nor much more info to add to this bug.  I hope this helps a little bit.

Version-Release number of selected component (if applicable):
whatever was available 08/24/09 (EST)

How reproducible:
only tried once.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Chris Lumens 2009-08-24 15:48:16 UTC 
Same question as the other bug report...

It'd be helpful to know what the save-to-bugzilla error was, though it's
probably related to the networking problem.  I'd still like to make it a
little more robust in the face of these sorts of issues since it's the bug
reporting system.
Comment 2 Chris Lumens 2009-08-24 17:37:51 UTC 
Okay, so the problem here is that there's no network enabled, so save-to-bugzilla presents an error message.  I think this is probably working about as well as can be expected.  We have a couple ways of detecting network problems and displaying errors about it, but bringing up the network in the face of dbus errors is pretty well outside the scope of python-meh.

So in summary, I think this is getting handled correctly.  Let's continue to track the networking in anaconda problem separately.