Bug 1308472

Summary: Local disk should display as "/dev/sd*" but not "/dev/mapper/xxx"
Product: Red Hat Enterprise Virtualization Manager Reporter: Wei Wang <weiwang>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED WORKSFORME QA Contact: Wei Wang <weiwang>
Severity: urgent Docs Contact:
Priority: high    
Version: 3.6.2CC: cshao, fdeutsch, gklein, huiwa, huzhao, leiwang, lsurette, weiwang, yaniwang, ycui, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-23 08:12:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/*.*
none
local-disk
none
sosreport
none
/etc
none
/config none

Description Wei Wang 2016-02-15 10:06:13 UTC
Created attachment 1127221 [details]
/var/log/*.*

Description of problem:
Local disk should display as "/dev/sd*" but not  "/dev/mapper/xxx"

Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.2-20160212.0
ovirt-node-3.6.1-6.0.el7ev.noarch

How reproducible:
100%


Steps to Reproduce:
1. TUI clean installed rhevh on local machine.
2. Enter "select the disk" page
3. Check device name in the device list


Actual results:
Device name display as "/dev/mapper/xxx"


Expected results:
Device name should display as "/dev/sd*"

Additional info:
No such issue in 7.2_3.5 build

Comment 1 Wei Wang 2016-02-15 10:07:56 UTC
Created attachment 1127222 [details]
local-disk

Comment 2 Fabian Deutsch 2016-02-16 11:49:03 UTC
What kind of machine is used?

What is the output of multipath -ll? (sosreport helps as well)

Comment 3 Wei Wang 2016-02-17 02:55:00 UTC
(In reply to Fabian Deutsch from comment #2)
> What kind of machine is used?
> 
Machine:Dell-760/790 
Hard disk: SAMSUNG_HD322GM
CPU: Intel(R) Core(TM)2 x86_64

> What is the output of multipath -ll? (sosreport helps as well)
multipath -ll
SAMSUNG_HD322GM_S2PAJ90B519911 dm-0 ATA ,SAMSUNG HD322GM
size=298G features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
`- 2:0:0:0 sda 8:0 active ready running

Comment 4 Fabian Deutsch 2016-02-17 08:26:50 UTC
Please also provide the sosreport and all of /etc and /config

Comment 5 Wei Wang 2016-02-18 02:38:27 UTC
Created attachment 1128126 [details]
sosreport

Comment 6 Wei Wang 2016-02-18 02:43:28 UTC
Created attachment 1128127 [details]
/etc

Comment 7 Wei Wang 2016-02-18 02:47:27 UTC
Created attachment 1128128 [details]
/config

Comment 8 Fabian Deutsch 2016-02-22 09:37:40 UTC
This behavior is okay in RHEV 3.6.

In RHEV 3.6 vdsm's multipath config is used right from the beginning, and vdsm is configuring to always use mapper names - even for single path devices.

For new 3.6 installations this should not be a problem.

What about upgrades? On a machine where in RHEV 3.5 /dev/sd* was used, does the upgrade work to RHEV-H 3.6?

Comment 9 Wei Wang 2016-02-22 09:55:34 UTC
Since during upgrades we cannot see the select page, so do we have another way to get the info which we want?

Comment 10 Fabian Deutsch 2016-02-22 13:42:26 UTC
The question is if upgrades are working, it is correct that you don't see the storage page.

Comment 11 Wei Wang 2016-02-23 06:20:20 UTC
Upgrades is successful from rhev-hypervisor7-7.2-20151129.1 to rhev-hypervisor7-7.2-20160212.0

Comment 12 Fabian Deutsch 2016-02-23 08:12:31 UTC
This is good news.

For now I don't see a risk in this change of devices witha  single path also appearing as mapper devices.

The only visual change is in the TUI: In 3.5 there was /dev/[hs]d*, in 3.6 there will be /dev/mapper/..
But this is only visual and does not have a functional impact.