Bug 495139

Summary: Anaconda traceback when installing with another LVM already existing
Product: [Fedora] Fedora Reporter: Andreas Thienemann <andreas>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 11CC: anaconda-maint-list, dwlegg, notting, pjones, rmaximo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: anaconda_trace_hash:c3d3536e03d2b364dcdeb778ea011efb682bffb615c2e9c9763fddb1e1b3b2e5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-17 18:03:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 495141    
Attachments:
Description Flags
Attached traceback automatically from anaconda.
none
parted output
none
vgdisplay output after anaconda crash none

Description Andreas Thienemann 2009-04-09 21:36:58 UTC
The following was filed automatically by anaconda:
anaconda 11.5.0.38 exception report
Traceback (most recent call first):
  File "/tmp/updates/storage/devicetree.py", line 1583, in devices
    raise DeviceTreeError("duplicate paths in device tree")
  File "/tmp/updates/storage/__init__.py", line 279, in devices
    devices = self.devicetree.devices.values()
  File "/tmp/updates/platform.py", line 59, in _mntDict
    for device in [d for d in self.anaconda.id.storage.devices if d.format.mountable]:
  File "/tmp/updates/platform.py", line 69, in bootDevice
    mntDict = self._mntDict()
  File "/tmp/updates/platform.py", line 382, in bootDevice
    return Platform.bootDevice(self)
  File "/tmp/updates/storage/__init__.py", line 214, in doIt
    boot = self.anaconda.platform.bootDevice()
  File "/tmp/updates/packages.py", line 115, in turnOnFilesystems
    anaconda.id.storage.doIt()
  File "/tmp/updates/dispatch.py", line 205, in moveStep
    rc = stepFunc(self.anaconda)
  File "/tmp/updates/dispatch.py", line 128, in gotoNext
    self.moveStep()
  File "/tmp/updates/gui.py", line 1323, in nextClicked
    self.anaconda.dispatch.gotoNext()
DeviceTreeError: duplicate paths in device tree

Comment 1 Andreas Thienemann 2009-04-09 21:37:13 UTC
Created attachment 339001 [details]
Attached traceback automatically from anaconda.

Comment 2 Andreas Thienemann 2009-04-09 21:40:44 UTC
Created attachment 339002 [details]
parted output

Comment 3 Andreas Thienemann 2009-04-09 21:41:55 UTC
Created attachment 339003 [details]
vgdisplay output after anaconda crash

Comment 4 Andreas Thienemann 2009-04-09 21:53:00 UTC
Planned partition layout:

sda1 ext3 /boot partition to be used for the rawhide installation (existing)
sda2 ntfs partition, should be left alone (existing)
sda3 ext3 /boot1 partition for a fc4 installation, should be chainloaded by the grub installed in sda (existing)
sda4 extended partition (existing)
sda5 lvm for a fc4 installation (existing)
sda6 encrypted lvm for the rawhide installation (newly created in the free space by anaconda)


Steps to reproduce:
1. Netboot anaconda
2. Select defaults leading up to the partitioning screen
3. Select Custom Layout
4. Click Next.
5. Select /dev/sda1 to be reformatted as ext3 and mounted as /boot
6. Create a new LVM partition, 17408MB large, select encrypted
7. Click LVM to edit this LVM partition named vg_workstation
8. ??? Wonder about the "Physical Volumes to Use:" list which contains luks-3 and luks-4 ???
9. Create lv root with 16384MB
10. Create lv swap with 1020MB
11. Click Next.
12. Crash.

Comment 5 Chris Lumens 2009-04-15 20:00:43 UTC
Did you happen to go back and forth from the custom partitioning screen to that initial "Use free space/Replace existing system/Etc." screen as part of your work?

Comment 6 Bill Nottingham 2009-05-29 02:49:40 UTC
Does this persist with the current RC images?

Comment 7 Bug Zapper 2009-06-09 13:34:36 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Chris Lumens 2009-06-11 20:26:19 UTC
*** Bug 505404 has been marked as a duplicate of this bug. ***