Hide Forgot
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
Created attachment 1127222 [details] local-disk
What kind of machine is used? What is the output of multipath -ll? (sosreport helps as well)
(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
Please also provide the sosreport and all of /etc and /config
Created attachment 1128126 [details] sosreport
Created attachment 1128127 [details] /etc
Created attachment 1128128 [details] /config
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?
Since during upgrades we cannot see the select page, so do we have another way to get the info which we want?
The question is if upgrades are working, it is correct that you don't see the storage page.
Upgrades is successful from rhev-hypervisor7-7.2-20151129.1 to rhev-hypervisor7-7.2-20160212.0
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.