Bug 683332 - storage_init parameter not consistent between auto & interactive install
Summary: storage_init parameter not consistent between auto & interactive install
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Mike Burns
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-09 06:53 UTC by Mohua Li
Modified: 2013-04-30 23:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-09 13:24:44 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Mohua Li 2011-03-09 06:53:46 UTC 
Description of problem:
n interactive install, we always use multipath to manage the device, it means user always see /dev/mapper/* intstead /dev/sd*, but in auto install, we actually could specify both /dev/sd*(local disk), /dev/mapper/*, it's quite confuse, we need to be consistent, 



Version-Release number of selected component (if applicable):
rhevh 6.1-8 

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Mike Burns 2011-03-09 13:24:44 UTC 
autoinstall is considered an advanced use case.  It was intentional that we added the ability to specify /dev/sdX or /dev/mapper/<wwid>.  Internally, we translate all devices to /dev/mapper/<wwid> and after installation, everything should be using the /dev/mapper device.  We also provide storage_init=scsi storage_init=usb, etc. for autoinstall which aren't available in the UI
Note You need to log in before you can comment on or make changes to this bug.