9:03 a.m.
hello
i'm adding a new host into ovirt
after the installation procces is finished I got an error: "VDSM kvm6
command ConnectStoragePoolVDS failed: Cannot find master domain".
on the vdsm server in /dev/disk/by-path/ i see the block device but
device-mapper not mappying it
then I found the master's lun in the blacklist:
/etc/multipath/conf.d/vdsm_blacklist.conf
why vdsm host put the lun wwn in blacklist and what I can do ?
addition info:
============
Ovirt-engine 4.4.7
vdsm server:
- OS Version: RHEL - 8.5 - 1.2111.el8
- OS Description: CentOS Linux 8
- Kernel Version: 4.18.0 - 348.2.1.el8_5.x86_64
- KVM Version: 6.0.0 - 33.el8
- LIBVIRT Version: libvirt-7.6.0-6.el8
- VDSM Version: vdsm-4.40.90.4-1.el8
the vdsm server has one link connection to the fc storage lun
10:44 a.m.
On Tuesday, 7 December 2021 09:03:17 CET david wrote:
hello
i'm adding a new host into ovirt
after the installation procces is finished I got an error: "VDSM kvm6
command ConnectStoragePoolVDS failed: Cannot find master domain".
on the vdsm server in /dev/disk/by-path/ i see the block device but
device-mapper not mappying it
then I found the master's lun in the blacklist:
/etc/multipath/conf.d/vdsm_blacklist.conf
why vdsm host put the lun wwn in blacklist and
Better to check /dev/disk/by-id/. Could you check the ID of this device is the same as one
in the blacklist?
If so, could you please also share output of
/usr/bin/lsblk --raw --noheadings --paths --inverse --include 253 --nodeps --output
type,name,mountpoint
and also VG info of this device:
vgs --readonly --config 'devices {filter=["a|.*|"]}' $VG_NAME
so we can analyze it?
what I can do ?
remove it from blacklist
addition info:
============
Ovirt-engine 4.4.7
vdsm server:
- OS Version: RHEL - 8.5 - 1.2111.el8
- OS Description: CentOS Linux 8
- Kernel Version: 4.18.0 - 348.2.1.el8_5.x86_64
- KVM Version: 6.0.0 - 33.el8
- LIBVIRT Version: libvirt-7.6.0-6.el8
- VDSM Version: vdsm-4.40.90.4-1.el8
the vdsm server has one link connection to the fc storage lun
5:56 p.m.
On Tue, Dec 7, 2021 at 10:04 AM david <dd432690(a)gmail.com> wrote:
hello
i'm adding a new host into ovirt
after the installation procces is finished I got an error: "VDSM kvm6 command
ConnectStoragePoolVDS failed: Cannot find master domain".
on the vdsm server in /dev/disk/by-path/ i see the block device but device-mapper not
mappying it
then I found the master's lun in the blacklist:
/etc/multipath/conf.d/vdsm_blacklist.conf
why vdsm host put the lun wwn in blacklist
When adding a host, we run:
vdsm-tool config-lvm-filter
This command put the LUN in the blacklist since it seems to be a local
disk used by the host. Did you have active logical volumes from this LUN
mounted on the host while the host was added to engine?
After you fix the issue (see Vojta reply), please run again:
vdsm-tool config-lvm-filter
The command may suggest to change the lvm filter, and blacklist the device.
Do not confirm and share the output.
Nir
9:21 a.m.
This command put the LUN in the blacklist since it seems to be a
local
disk used by the host.
yes, but in fact this disk is a remote block device from fc storage
Did you have active logical volumes from this LUN mounted on the host
while the host was added to engine?
I installed only Centos, updated it and connected the Ovirt repository,
all another settings were made by Engine himself
11:03 a.m.
After you fix the issue (see Vojta reply), please run again:
vdsm-tool config-lvm-filter
The command may suggest to change the lvm filter, and blacklist the device.
Do not confirm and share the output.
removed line wwid "3600000e00d11000000113629000e0000" from vdsm_blacklist.conf
and ran vdsm-tool config-lvm-filter
here is the command output:
Analyzing host...
Found these mounted logical volumes on this host:
This is the recommended LVM filter for this host:
filter = [ "r|.*|" ]
This filter allows LVM to access the local devices used by the
hypervisor, but not shared storage owned by Vdsm. If you add a new
device to the volume group, you will need to edit the filter manually.
This is the current LVM filter:
filter = [ "r|.*|" ]
To use the recommended filter we need to add multipath
blacklist in /etc/multipath/conf.d/vdsm_blacklist.conf:
blacklist {
wwid "3600000e00d11000000113629000e0000"
wwid "3600605b010bbc0e029275d23bba8027b"
}
9:20 a.m.
Could you check the ID of this device is the same as one in the
blacklist?
yes it is same:
# /dev/disk/by-id
=======================
lvm-pv-uuid-GqZf9p-oyaL-dLN4-RdxE-Ll6Y-1Gjn-B6F4sX -> ../../sdb
scsi-3600000e00d11000000113629000e0000 -> ../../sdb
scsi-3600605b010bbc0e029275d23bba8027b -> ../../sda
lscsi-3600605b010bbc0e029275d23bba8027b-part1 -> ../../sda1
scsi-3600605b010bbc0e029275d23bba8027b-part2 -> ../../sda2
scsi-3600605b010bbc0e029275d23bba8027b-part3 -> ../../sda3
scsi-3600605b010bbc0e029275d23bba8027b-part4 -> ../../sda4
scsi-3600605b010bbc0e029275d23bba8027b-part5 -> ../../sda5
scsi-SFTS_PRAID_EP520i_007b02a8bb235d2729e0c0bb10b00506 -> ../../sda
scsi-SFTS_PRAID_EP520i_007b02a8bb235d2729e0c0bb10b00506-part1 -> ../../sda1
scsi-SFTS_PRAID_EP520i_007b02a8bb235d2729e0c0bb10b00506-part2 -> ../../sda2
scsi-SFTS_PRAID_EP520i_007b02a8bb235d2729e0c0bb10b00506-part3 -> ../../sda3
scsi-SFTS_PRAID_EP520i_007b02a8bb235d2729e0c0bb10b00506-part4 -> ../../sda4
scsi-SFTS_PRAID_EP520i_007b02a8bb235d2729e0c0bb10b00506-part5 -> ../../sda5
scsi-SFUJITSU_ETERNUS_DXL_113629 -> ../../sdb
wwn-0x600000e00d11000000113629000e0000 -> ../../sdb
wwn-0x600605b010bbc0e029275d23bba8027b -> ../../sda
wwn-0x600605b010bbc0e029275d23bba8027b-part1 -> ../../sda1
wwn-0x600605b010bbc0e029275d23bba8027b-part2 -> ../../sda2
wwn-0x600605b010bbc0e029275d23bba8027b-part3 -> ../../sda3
wwn-0x600605b010bbc0e029275d23bba8027b-part4 -> ../../sda4
wwn-0x600605b010bbc0e029275d23bba8027b-part5 -> ../../sda5
# /etc/multipath/conf.d/vdsm_blacklist.conf
===============================================
# This file is managed by vdsm, do not edit!
# Any changes made to this file will be overwritten when running:
# vdsm-tool config-lvm-filter
blacklist {
wwid "3600000e00d11000000113629000e0000"
wwid "3600605b010bbc0e029275d23bba8027b"
}
/usr/bin/lsblk --raw --noheadings --paths --inverse --include 253
--nodeps --output type,name,mountpoint
=================================
empty output of above command
vgs --readonly --config 'devices
{filter=["a|.*|"]}' $VG_NAME
====================================
VG #PV #LV #SN Attr VSize VFree
2047ffc7-cb32-4663-81ad-7f4e0becdf13 1 13 0 wz--n- 544.62g 41.00g
remove it from blacklist
but the message in the vdsm_blacklist.conf warns me against manual editing.
Ignore ?
12:51 p.m.
> /usr/bin/lsblk --raw --noheadings --paths --inverse --include
253 --nodeps
> --output type,name,mountpoint
=================================
empty output of above command
could you run it again, but instead of "--include 253" use number you get when
run
cat /proc/devices |grep device-mapper| cut -f 1 -d ' '
i.e.
INC=`cat /proc/devices |grep device-mapper| cut -f 1 -d ' '` &&
/usr/bin/lsblk --raw --noheadings --paths --inverse --include $INC --nodeps --output
type,name,mountpoint
> vgs --readonly --config 'devices {filter=["a|.*|"]}' $VG_NAME
====================================
VG #PV #LV #SN Attr VSize VFree
2047ffc7-cb32-4663-81ad-7f4e0becdf13 1 13 0 wz--n- 544.62g 41.00g
sorry, I was interested in LV tags, i.e. the command should be
lvs --readonly --config 'devices {filter=["a|.*|"]}' --options
vg_name,vg_tags /dev/sdb
> remove it from blacklist
but the message in the vdsm_blacklist.conf warns me against manual editing.
Ignore ?
yes, it won't be overwritten until you run "vdsm-tool config-lvm-filter" and
confirm you
want to overwrite it
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/ List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MLBFU56KZTUJW
NCPKPYC5AS5RWBGSSWK/
1:35 p.m.
could you run it again, but instead of "--include 253" use
number you get when
run
cat /proc/devices |grep device-mapper| cut -f 1 -d ' '
253
INC=`cat /proc/devices |grep device-mapper| cut -f 1 -d '
'` &&
/usr/bin/lsblk --raw --noheadings --paths --inverse --include $INC --nodeps --output
type,name,mountpoint
still empty
lvs --readonly --config 'devices
{filter=["a|.*|"]}' --options vg_name,vg_tags /dev/sdb
Volume group "sdb" not found
Cannot process volume group sdb
yes, it won't be overwritten until you run "vdsm-tool
config-lvm-filter" and confirm you want to overwrite it
here is the command
output:
Analyzing host...
Found these mounted logical volumes on this host:
This is the recommended LVM filter for this host:
filter = [ "r|.*|" ]
This filter allows LVM to access the local devices used by the
hypervisor, but not shared storage owned by Vdsm. If you add a new
device to the volume group, you will need to edit the filter manually.
This is the current LVM filter:
filter = [ "r|.*|" ]
To use the recommended filter we need to add multipath
blacklist in /etc/multipath/conf.d/vdsm_blacklist.conf:
blacklist {
wwid "3600000e00d11000000113629000e0000"
wwid "3600605b010bbc0e029275d23bba8027b"
}
Configure host? [yes,NO] no
889
days inactive
891
days old
7 comments
3 participants
participants (3)
-
david -
Nir Soffer -
Vojtech Juranek