Bug 511169 - anaconda addUdevDevice
Summary: anaconda addUdevDevice
Keywords:
Status: CLOSED DUPLICATE of bug 510033
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: ppc
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: anaconda_trace_hash:0b403cbf8524b7b5d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-14 00:26 UTC by Geoff Levand
Modified: 2009-07-14 15:35 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-14 15:35:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (44.96 KB, text/plain)
2009-07-14 00:26 UTC, Geoff Levand
no flags Details

Description Geoff Levand 2009-07-14 00:26:45 UTC
The following was filed automatically by anaconda:
anaconda 12.2 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/storage/devicetree.py", line 1286, in addUdevDevice
    if device.name in self.protectedDevNames:
  File "/usr/lib/anaconda/storage/devicetree.py", line 1791, in populate
    self.addUdevDevice(dev)
  File "/usr/lib/anaconda/storage/__init__.py", line 291, in reset
    self.devicetree.populate()
  File "/usr/lib/anaconda/storage/__init__.py", line 92, in storageInitialize
    storage.reset()
  File "/usr/lib/anaconda/dispatch.py", line 204, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 127, in gotoNext
    self.moveStep()
  File "/usr/lib/anaconda/text.py", line 721, in run
    anaconda.dispatch.gotoNext()
  File "/usr/bin/anaconda", line 964, in <module>
    anaconda.intf.run(anaconda)
AttributeError: 'NoneType' object has no attribute 'name'

Comment 1 Geoff Levand 2009-07-14 00:26:49 UTC
Created attachment 351541 [details]
Attached traceback automatically from anaconda.

Comment 2 Chris Lumens 2009-07-14 15:35:43 UTC

*** This bug has been marked as a duplicate of bug 510033 ***


Note You need to log in before you can comment on or make changes to this bug.