Hide Forgot
Description of problem: Anaconda crashes every time I try to install using multipath devices. Version-Release number of selected component (if applicable): Fedora 16's DVD (provided) How reproducible: Try to install using multipath on a: 08:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) Steps to Reproduce: 1. Start the installation (DVD or network) 2. Get to the point where you choose the installation storage mode 3. Choose advanced 4. Select the Flash HDD (8 Gb) provided (not under the storage controller) 5. Go to multipath section and select all of the devices 6. Watch it crash Actual results: I have a video. I dunno if I should post it since it's 71MB. I will provide it online. Expected results: Normal installation Additional info: When using advanced storage and using the 8GB Flash HDD only, the installation runs smoothly. I could provide access in order to debug if needed. Link to errors video: http://downloads.woralelandia.com/errors.avi
Please attach the /tmp/anaconda-tb-* file to this bug report.
I've gathered a bit of info. Everything is available in: http://downloads.woralelandia.com/fedora/ Please, get what you might need. Also, I will attach the file you asked to the bug.
Created attachment 548973 [details] the anaconda tb file the file you requested
I just want to add that this seems to work perfectly fine on CentOS 6.1 installation (network). Haven't tried the DVD.
Created attachment 549084 [details] a lot of multipath devices on the "basic drives" section
Created attachment 549085 [details] a lot of multipath devices missing this one compliments the basic_drives screenshot
This exception is raised when executing 'kpartx -a -p p self.path' (where self.path equals to '/dev/mapper/MAP_NAME_OF_THE_DEVICE') exits with return code different from '0'. It can be seen in the attachment #1 [details] that in this case it was '1'. lvm-team, can you please tell us in which cases kpartx returns '1' as exit code?
*** Bug 769486 has been marked as a duplicate of this bug. ***
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
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.