Bug 456112

Summary: Kickstart installation fails with python error: ends with '/' and is not just '/'
Product: [Fedora] Fedora Reporter: Bevis King <brwk>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 9   
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: 2008-07-21 16:50:35 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:

Description Bevis King 2008-07-21 15:49:07 UTC
Description of problem:
Attempt to install Fedora 9 on Dell Optiplex GX620 fails with the following output:
  File "/usr/lib64/python2.5/site-packages/rhpxl/videocard.py", line 135, in __
nit__
    devs = [bus.get_object('org.freedesktop.Hal',x) for x in devs]
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 237, in __init__
    _dbus_bindings.validate_object_path(object_path)
ValueError: Invalid object path '/org/freedesktop/Hal/devices/storage_model_SAMS
UNG_HD160JJ/': ends with '/' and is not just '/'
install exited abnormally [1/1]

(this is all the information remaining on the console)


Version-Release number of selected component (if applicable):
Fedora 9

How reproducible:
Every time on this hardware (using kickstart)

Steps to Reproduce:
1.  Kickstart machine with DVD installation media as boot disc
  
Actual results:
Crash as per above.

Expected results:
Installation begins...

Additional info:

Comment 1 Bevis King 2008-07-21 16:00:07 UTC
Switching to a text mode install didn't help.

The Hard Drive ID as reported by the BIOS is:

SAMSUNG HD160JJ/P

Looks like the script can't cope with there being a '/' in the reported drive ID!

Ooops!


Comment 2 Bevis King 2008-07-21 16:12:02 UTC
OK, swapping the hard drive for a different one with out a / in the BIOS
reported name causes exactly the same kickstart configuration to work just fine!



Comment 3 Jeremy Katz 2008-07-21 16:50:35 UTC

*** This bug has been marked as a duplicate of 442457 ***