Bug 1185759 - Should not list the single path disk in "#multipath -ll" command after register to rhevm
Summary: Should not list the single path disk in "#multipath -ll" command after regist...
Keywords:
Status: CLOSED DUPLICATE of bug 1173290
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-26 08:52 UTC by wanghui
Modified: 2015-01-26 09:01 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-26 09:01:07 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
log files (133.41 KB, application/x-gzip)
2015-01-26 08:52 UTC, wanghui
no flags Details

Description wanghui 2015-01-26 08:52:47 UTC
Created attachment 984131 [details]
log files

Description of problem:
It should not list the single path disk in "#multipath -ll" command after register to rhevm.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.6-20150123.0.iso
ovirt-node-3.0.1-19.el6.27.noarch

How reproducible:
100%

Steps to Reproduce:
1. TUI install rhev-hypervisor6-6.6-20150123.0.iso
2. Check the output of "#multipath -ll"
3. Register to rhevm3.4
4. Check the output of "#multipath -ll"

Actual results:
1. After step2, the output is as follows.
# multipath -ll
Jan 26 07:30:24 | multipath.conf line 4, duplicate keyword: getuid_callout

2. After step4, the output is as follows. 
# multipath -ll
360050763008084e6e00000000000000b dm-7 IBM,2145
size=50G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=10 status=active
  `- 0:0:0:3 sdd 8:48 active ready running
360050763008084e6e00000000000000a dm-6 IBM,2145
size=40G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=50 status=active
  `- 0:0:0:2 sdc 8:32 active ready running
360050763008084e6e000000000000009 dm-5 IBM,2145
size=30G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=10 status=active
  `- 0:0:0:1 sdb 8:16 active ready running

# lsblk 
NAME                      MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
loop0                       7:0    0 159.9M  1 loop  
loop1                       7:1    0   1.5G  1 loop  
└─live-rw (dm-0)          253:0    0   1.5G  0 dm    /
loop2                       7:2    0   512M  0 loop  
└─live-rw (dm-0)          253:0    0   1.5G  0 dm    /
sda                         8:0    0    20G  0 disk  
├─sda1                      8:1    0   243M  0 part  
├─sda2                      8:2    0   244M  0 part  
├─sda3                      8:3    0   244M  0 part  /dev/.initramfs/live
└─sda4                      8:4    0  19.3G  0 part  
  ├─HostVG-Swap (dm-1)    253:1    0   9.8G  0 lvm   [SWAP]
  ├─HostVG-Config (dm-2)  253:2    0     8M  0 lvm   /config
  ├─HostVG-Logging (dm-3) 253:3    0     2G  0 lvm   /var/log
  └─HostVG-Data (dm-4)    253:4    0   7.4G  0 lvm   /data
sdb                         8:16   0    30G  0 disk  
└─360050763008084e6e000000000000009 (dm-5)
                          253:5    0    30G  0 mpath 
sdc                         8:32   0    40G  0 disk  
└─360050763008084e6e00000000000000a (dm-6)
                          253:6    0    40G  0 mpath 
sdd                         8:48   0    50G  0 disk  
└─360050763008084e6e00000000000000b (dm-7)
                          253:7    0    50G  0 mpath 

Expected results:
1. It should keep the same output before and after register to rhevm in rhevh. So it should not list the single path after register to rhevm also. 

Additional info:

Comment 1 Fabian Deutsch 2015-01-26 09:01:07 UTC
This is a side effect of bug 1173290. sda, which is used for booting was not claimed, because it is already in use, so there should be not functional impact on the core RHEV-H functionality.

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


Note You need to log in before you can comment on or make changes to this bug.