Bug 683332

Summary:	storage_init parameter not consistent between auto & interactive install
Product:	Red Hat Enterprise Linux 6	Reporter:	Mohua Li <moli>
Component:	ovirt-node	Assignee:	Mike Burns <mburns>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	gouyang, leiwang, mburns, moli, mshao, ovirt-maint, ycui
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-09 13:24:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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