Bug 492470

Summary: traceback from the automated file-a-bugzilla
Product: [Fedora] Fedora Reporter: Dave Jones <davej>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: anaconda-maint-list, pfrields, pjones, rmaximo, 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-06-25 17:36:17 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:
Attachments:
Description Flags
traceback whilst filing bug none

Description Dave Jones 2009-03-26 21:26:13 UTC
Created attachment 336903 [details]
traceback whilst filing bug

I got a traceback, and tried to let it file a bugzilla automatically.
This resulted in another traceback, and afaik, no filed bug.

attached photo is traceback.

Comment 1 Dave Jones 2009-03-26 21:28:05 UTC
looks like for whatever reason, it couldn't resolve the hostname.

Which is odd, because it resolves fine when I try it from a command line.

Comment 2 Chris Lumens 2009-04-14 17:51:18 UTC
I don't have an explanation for not being able to resolve the hostname, but we could at least catch the exception.  I've modified anaconda so we'll display a helpful dialog instead of exploding.  If you're able to reproduce this, we'll proceed with trying to track that down.

Comment 3 Bug Zapper 2009-06-09 12:42:48 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping