The following was filed automatically by anaconda: anaconda 12.11 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicetree.py", line 1996, in devices raise DeviceTreeError("duplicate paths in device tree") File "/usr/lib/anaconda/storage/__init__.py", line 317, in disks for device in self.devicetree.devices: File "/usr/lib/anaconda/storage/partitioning.py", line 355, in removeEmptyExtendedPartitions for disk in storage.disks: File "/usr/lib/anaconda/storage/partitioning.py", line 351, in clearPartitions removeEmptyExtendedPartitions(storage) File "/usr/lib/anaconda/storage/partitioning.py", line 174, in doAutoPartition clearPartitions(anaconda.id.storage) 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/gui.py", line 1201, in nextClicked self.anaconda.dispatch.gotoNext() DeviceTreeError: duplicate paths in device tree
Created attachment 356895 [details] Attached traceback automatically from anaconda.
Testing JKeating anaconda 12.11 boot.iso and selected "replace existing Linux system", checked "Review and modify partitioning layout" and clicked Next. Related to 516557?
In view of 516557, 516567, and 516575, shouldn't these be higher priority and severity since they prevent the installation of fedora?
Created attachment 357042 [details] Attached traceback automatically from anaconda.
This is 12.13 and the bzs in comment 3 prevent installation. I can't get past the select partitioning method screen. I know this test system is a corner case, but these failures should not now be occurring. I am basing this on: 1) Fedora 11 final at least allowed updating an existing fedora installation; 2) I installed suse 11.2 milestone 4 this week and used their equivalent of custom partitioning layout with success; and 3), installed ubuntu 9.04 without any issues. I know these issues will be fixed and I will patiently test any fixes, but at some point I may have to ditch this system's current partitioning and allow anaconda to do a totally fresh install on a bare system and then try to recreate, a step at a time, the current configuration until the real issues are detected. This would take an incredible amount of time (days if not weeks), but I may be willing to take the time if it will help. I don't know what kind of so called production systems use fedora, but there must be some that are more complex than this system. If they don't use fedora, they use RHEL, and eventually will have this version of anaconda to contend with. Anaconda, at this stage, is just not a robust piece of software.
First, thanks for your efforts in testing and debugging these problems. The entire storage subsystem of anaconda was rewritten for F11, in case you were not aware of it. Storage configurations can be arbitrarily complex and/or convoluted, and it simply takes time to encounter many of the more bizarre scenarios, like your setup which uses partitions as members of a biosraid array (bug 516557). Sometimes the bugs you find when doing strange things indicate problems in anaconda (this bug being one such case) -- other times they are just corner case usage that we frankly do not give a high priority to (bug 516557 is an example). We continue to work through the remaining storage issues as quickly as possible. Thanks again for the testing coverage and persistence.
Can you briefly describe, to whatever extent is possible, what you had done and what was happening when this error occurred?
used 20090811 boot.iso from kojipkgs.../mash/rawhide/x86_64/os/images, burned to cd. booted with method=http://kojipkgs...etc selinuzx=0 normal startup, went thru finding storage devices normal set hostname, timezone and root passwords in select partitioning screen selected custom layout and got traceback after clicking next. rebooted and tried replace existing linux system and got traceback after clicking next.
Created attachment 357334 [details] Attached traceback automatically from anaconda.
anaconda 12.14 Still can't find an installation method that allows me to get past the select partitioning method screen. In this test I selected "replace existing linux system" and clicked next and after a short wait, traceback. If this traceback is due to mdadm containers then two things: 1) I deleted the container before the test and zero'd the superblock (the container had not been used, just created with 11 10G partitions); and, 2) even tho containers are not supported by anaconda, there should not be a traceback. Just ignore them as suse and ubuntu do.
I can't test this at present since I deleted all of the partitions that were in the container. When time permits, I will recreate the scenario and see what happens.
There is no need to retest at this time unless you just want to. Nothing has been done to address this specific problem, so there is no reason to expect a different result.
*** Bug 507253 has been marked as a duplicate of this bug. ***
I will try to recreate this scenario during F13 development. Stay tuned.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 504829 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
No point in keeping this open. Fedora/Anaconda have moved on and the installer is much more robust and versatile.