Bug 947422 - DeviceTreeError: MD RAID device None already in devicetree as 2
Summary: DeviceTreeError: MD RAID device None already in devicetree as 2
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d96c6757fc1a30dc9cf700dd7c6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-02 11:35 UTC by tommylovell
Modified: 2013-12-21 14:54 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-21 14:54:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda-tb (662.59 KB, text/plain)
2013-04-02 11:35 UTC, tommylovell
no flags Details
File: anaconda.log (7.56 KB, text/plain)
2013-04-02 11:35 UTC, tommylovell
no flags Details
File: environ (780 bytes, text/plain)
2013-04-02 11:35 UTC, tommylovell
no flags Details
File: ifcfg.log (485 bytes, text/plain)
2013-04-02 11:35 UTC, tommylovell
no flags Details
File: packaging.log (163.06 KB, text/plain)
2013-04-02 11:35 UTC, tommylovell
no flags Details
File: program.log (39.62 KB, text/plain)
2013-04-02 11:35 UTC, tommylovell
no flags Details
File: storage.log (191.49 KB, text/plain)
2013-04-02 11:35 UTC, tommylovell
no flags Details
File: syslog (105.09 KB, text/plain)
2013-04-02 11:35 UTC, tommylovell
no flags Details

Description tommylovell 2013-04-02 11:35:23 UTC
Description of problem:
Anaconda GUI installation apparently crashed while I was in the shell setting up RAID and mkfs'ing filesystems.  When I return to the GUI it stated that it had crashed.
The following was filed automatically by anaconda:
anaconda 18.37.11 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 776, in addUdevMDDevice
    "devicetree as %s" % (name, device.name))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1067, in addUdevDevice
    device = self.addUdevMDDevice(info)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1894, in _populate
    self.addUdevDevice(dev)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1842, in populate
    self._populate()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 428, in reset
    self.devicetree.populate(cleanupOnly=cleanupOnly)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 408, in _doExecute
    self.storage.reset()
  File "/usr/lib64/python2.7/threading.py", line 504, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run
    threading.Thread.run(self, *args, **kwargs)
DeviceTreeError: MD RAID device None already in devicetree as 2

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 quiet rd.live.check BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.6.10-4.fc18.x86_64
other involved packages: 
package:        anaconda-18.37.11
product:        Fedora
release:        Cannot get release name.
type:           libreport
version:        18

Comment 1 tommylovell 2013-04-02 11:35:27 UTC
Created attachment 730700 [details]
File: anaconda-tb

Comment 2 tommylovell 2013-04-02 11:35:29 UTC
Created attachment 730701 [details]
File: anaconda.log

Comment 3 tommylovell 2013-04-02 11:35:31 UTC
Created attachment 730702 [details]
File: environ

Comment 4 tommylovell 2013-04-02 11:35:33 UTC
Created attachment 730703 [details]
File: ifcfg.log

Comment 5 tommylovell 2013-04-02 11:35:35 UTC
Created attachment 730704 [details]
File: packaging.log

Comment 6 tommylovell 2013-04-02 11:35:37 UTC
Created attachment 730705 [details]
File: program.log

Comment 7 tommylovell 2013-04-02 11:35:39 UTC
Created attachment 730706 [details]
File: storage.log

Comment 8 tommylovell 2013-04-02 11:35:41 UTC
Created attachment 730707 [details]
File: syslog

Comment 9 Fedora End Of Life 2013-12-21 12:36:32 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.


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