Bug 491927

Summary: DeviceError: parent device does not exist
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: anaconda-maint-list, george, jturner, pjones, rmaximo, tcallawa, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: anaconda_trace_hash:86d5f83cb5150c3ba61d9e893c7eab05c3d02ae609f9b23a32ca2eb4c8c329a1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-27 15:20:15 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 495965    
Description Flags
Attached traceback automatically from anaconda. none

Description James Laska 2009-03-24 12:57:53 EDT
The following was filed automatically by anaconda:
anaconda exception report
Traceback (most recent call first):
  File "/tmp/updates/storage/devices.py", line 262, in createParents
    raise DeviceError("parent device does not exist")
  File "/tmp/updates/storage/devices.py", line 1650, in create
  File "/tmp/updates/storage/deviceaction.py", line 206, in execute
  File "/tmp/updates/storage/devicetree.py", line 659, in processActions
  File "/tmp/updates/storage/__init__.py", line 211, in doIt
  File "/tmp/updates/packages.py", line 115, in turnOnFilesystems
  File "/tmp/updates/dispatch.py", line 205, in moveStep
    rc = stepFunc(self.anaconda)
  File "/tmp/updates/dispatch.py", line 128, in gotoNext
  File "/tmp/updates/gui.py", line 1317, in nextClicked
DeviceError: parent device does not exist
Comment 1 James Laska 2009-03-24 12:57:58 EDT
Created attachment 336498 [details]
Attached traceback automatically from anaconda.
Comment 2 James Laska 2009-03-24 13:03:29 EDT
Steps to reproduce:
 1) Boot rawhide/i386 on KVM guest
 2) Add remote iSCSI drive (IP:, IQN:iqn.rhel5.i386)
 3) Select the local KVM disk ('vda') as the boot drive
 4) Select "Use entire disk" and [X] Review partition selections
 5) Click Next 
 6) (optional) ... rearrange partitions to ensure that 'vda' gets the /boot partition
 7) Click Next
Comment 3 David Lehman 2009-04-16 12:13:40 EDT
Can you retest this at your convenience? I expect that it was fixed shortly after beta.
Comment 4 Chris Lumens 2009-04-17 11:36:18 EDT
*** Bug 496116 has been marked as a duplicate of this bug. ***
Comment 5 James Laska 2009-04-27 15:20:15 EDT
Tested and confirmed fixed with anaconda-