Bug 767950

Summary: DeviceTreeError: MD RAID device md127 not in devicetree after scanning all slaves
Product: [Fedora] Fedora Reporter: Michael Glasgow <michael.glasgow>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, jonathan, michael.glasgow, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 08:44:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
anaconda exception report
none
anaconda-tb-* none

Description Michael Glasgow 2011-12-15 11:08:17 UTC
Created attachment 547182 [details]
anaconda exception report

Anaconda crashes during initial scan of storage devices.

See attachment for details.

Comment 1 Michael Glasgow 2011-12-15 11:09:51 UTC
FYI, anaconda's "save" option incorrectly detects this as a duplicate of bug 731177 and refuses to let me upload from the GUI, so I had to create this bug by hand.

Comment 2 Chris Lumens 2011-12-15 18:05:54 UTC
Please attach the /tmp/anaconda-tb-* file as a single attachment, not as part of an archive.  When you attach an archive, it becomes much more difficult to search through bugzilla later.  Thanks.

Comment 3 Michael Glasgow 2011-12-15 20:44:21 UTC
Created attachment 547478 [details]
anaconda-tb-*

Requested file attached.  When the anaconda save option fails to save the bug, it becomes more difficult to do all this stuff manually.

Comment 4 Brian Lane 2012-02-20 16:42:24 UTC
What install media are you using? Your /proc/cmdline is empty. Any other details of your system would be helpful.

Comment 5 Michael Glasgow 2012-02-21 06:50:15 UTC
This was using the network install cd:

http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/x86_64/iso/Fedora-16-x86_64-netinst.iso

The system is a Lenovo Thinkpad T420 laptop.

Comment 6 Jesse Keating 2012-07-19 21:13:55 UTC
Is this still an issue under Fedora 17?  If so, please attach a new set of logs.

Comment 7 Fedora End Of Life 2013-01-16 10:12:30 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Fedora End Of Life 2013-02-13 08:44:45 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.