Thank you very much Semi. The reinstallation would not be an problem, being the fact that i've spent so much in sorting this issue. I don't understant the "setup a blacklist part" . What does this mean, how should I do it ? I have looked over the other oVirt nodes that I have in the network, and the mpath is active on their rootfs as well. I have used the 4.2-2018052606.iso image for instalation for cluster nodes and for single instance too. Would it be possible to have a bug in this version ? What iso should I use just to be sure everything will work good ? Again, thank you very much ! On Tue, Jun 12, 2018, 21:54 femi adegoke <ovirt(a)fateknollogee.com&gt; wrote:

Fortunatelly, after node reinstallation nu more mpath devices are present: multipath -ll Jun 13 06:32:10 | DM multipath kernel driver not loaded Jun 13 06:32:10 | DM multipath kernel driver not loaded But now I am encountering this "invalid number format \"virt\" in option \"brick-uid": TASK [Sets options for volume] ******************************************************************************************************************************************* failed: [10.10.8.111] (item={u'key': u'storage.owner-uid', u'value': u'virt'}) => {"changed": false, "item": {"key": "storage.owner-uid", "value": "virt"}, "msg": "volume set: failed: invalid number format \"virt\" in option \"brick-uid\"\n"} changed: [10.10.8.111] => (item={u'key': u'storage.owner-gid', u'value': u'36'}) failed: [10.10.8.111] (item={u'key': u'features.shard', u'value': u'36'}) => {"changed": false, "item": {"key": "features.shard", "value": "36"}, "msg": "volume set: failed: Error, Validation Failed\n"} changed: [10.10.8.111] => (item={u'key': u'performance.low-prio-threads', u'value': u'30'}) changed: [10.10.8.111] => (item={u'key': u'performance.strict-o-direct', u'value': u'on'}) changed: [10.10.8.111] => (item={u'key': u'network.remote-dio', u'value': u'off'}) failed: [10.10.8.111] (item={u'key': u'network.ping-timeout', u'value': u'enable'}) => {"changed": false, "item": {"key": "network.ping-timeout", "value": "enable"}, "msg": "volume set: failed: invalid time format \"enable\" in \"option ping-timeout\"\n"} Below, is my gdeploy.conf: [hosts] 10.10.8.111 [script1] action=execute ignore_script_errors=no file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h 10.10.8.111 [disktype] jbod [diskcount] 12 [stripesize] 256 [service1] action=enable service=chronyd [service2] action=restart service=chronyd [shell2] action=execute command=vdsm-tool configure --force [script3] action=execute file=/usr/share/gdeploy/scripts/blacklist_all_disks.sh ignore_script_errors=no [pv] action=create devices=sdb ignore_pv_errors=no [vg1] action=create vgname=gluster_vg_sdb pvname=sdb ignore_vg_errors=no [lv1] action=create poolname=gluster_thinpool_sdb ignore_lv_errors=no vgname=gluster_vg_sdb lvtype=thinpool size=804GB poolmetadatasize=4GB [lv2] action=create lvname=gluster_lv_engine ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/engine size=100GB lvtype=thick [lv3] action=create lvname=gluster_lv_data ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/data lvtype=thinlv poolname=gluster_thinpool_sdb virtualsize=400GB [lv4] action=create lvname=gluster_lv_vmstore ignore_lv_errors=no vgname=gluster_vg_sdb mount=/gluster_bricks/vmstore lvtype=thinlv poolname=gluster_thinpool_sdb virtualsize=400GB [selinux] yes [service3] action=restart service=glusterd slice_setup=yes [firewalld] action=add ports=111/tcp,2049/tcp,54321/tcp,5900/tcp,5900-6923/tcp,5666/tcp,16514/tcp,54322/tcp services=glusterfs [script2] action=execute file=/usr/share/gdeploy/scripts/disable-gluster-hooks.sh [shell3] action=execute command=usermod -a -G gluster qemu [volume1] action=create volname=engine transport=tcp key=storage.owner-uid,storage.owner-gid,features.shard,performance.low-prio-threads,performance.strict-o-direct,network.remote-dio,network.ping-timeout,user.cifs,nfs.disable,performance.quick-read,performance.read-ahead,performance.io-cache,cluster.eager-lock value=36,36,on,32,on,off,30,off,on,off,off,off,enable #key=group,storage.owner-uid,storage.owner-gid,network.ping-timeout,performance.strict-o-direct,network.remote-dio,cluster.granular-entry-heal value=virt,36,36,30,on,off,enable #brick_dirs=10.10.8.111:/gluster_bricks/engine/engine brick_dirs=/gluster_bricks/engine/engine ignore_volume_errors=no [volume2] action=create volname=data transport=tcp key=storage.owner-uid,storage.owner-gid,features.shard,performance.low-prio-threads,performance.strict-o-direct,network.remote-dio,network.ping-timeout,user.cifs,nfs.disable,performance.quick-read,performance.read-ahead,performance.io-cache,cluster.eager-lock value=36,36,on,32,on,off,30,off,on,off,off,off,enable #key=group,storage.owner-uid,storage.owner-gid,network.ping-timeout,performance.strict-o-direct,network.remote-dio,cluster.granular-entry-heal value=virt,36,36,30,on,off,enable #brick_dirs=10.10.8.111:/gluster_bricks/data/data brick_dirs=/gluster_bricks/data/data ignore_volume_errors=no [volume3] action=create volname=vmstore transport=tcp key=storage.owner-uid,storage.owner-gid,features.shard,performance.low-prio-threads,performance.strict-o-direct,network.remote-dio,network.ping-timeout,user.cifs,nfs.disable,performance.quick-read,performance.read-ahead,performance.io-cache,cluster.eager-lock value=36,36,on,32,on,off,30,off,on,off,off,off,enable #key=group,storage.owner-uid,storage.owner-gid,network.ping-timeout,performance.strict-o-direct,network.remote-dio,cluster.granular-entry-heal value=virt,36,36,30,on,off,enable #brick_dirs=10.10.8.111:/gluster_bricks/vmstore/vmstore brick_dirs=/gluster_bricks/vmstore/vmstore ignore_volume_errors=no I just don't understand how this config should be adjusted so the ansible script will finnish succesfully... :( On Wed, Jun 13, 2018 at 9:06 AM, femi adegoke <ovirt(a)fateknollogee.com&gt; wrote: -- Best regards, Leo David

That was just me being stupid.... I was passing wrong values to the key for volumes. I am running again the playbook. On Wed, Jun 13, 2018 at 10:22 AM, femi adegoke <ovirt(a)fateknollogee.com&gt; wrote: -- Best regards, Leo David

Thank you, The playbook just finnished successfully. Now: 1. Should I create the blacklist acordingly: kblacklist { wwid INTEL_SSDSCKHB120G4_BTWM65160025120B wwid eui.0025385171b04d62 wwid SAMSUNG_MZ7GE960HMHP-000AZ_S1P8NYAG123827 } - but not sure what to put as wwid 2. How to deploy self-hosted engine vm, since when I hit any of the "Hosted engine" or "Hyperconverged" it does not recognize the already gluster setup ? 3. Will I be able to create some future gluster volumes using the other unused hdds ? From Cockpit, or again using gdeploy ? I am really sorry if i put stupid questions, but i just don't understand how to proceed further On Wed, Jun 13, 2018 at 10:23 AM, femi adegoke <ovirt(a)fateknollogee.com&gt; wrote: -- Best regards, Leo David

Gluster volumes are started, so I assume that the gluster part is fine. Would'nt make more sense to add everything to black list, reboot the server and continue with ovirt-engine vm setup ( and adding 10.10.8.111:/engine for vm storage ) ? ie: blacklist { devnode "*" } Thank you ! On Wed, Jun 13, 2018 at 11:05 AM, femi adegoke <ovirt(a)fateknollogee.com&gt; wrote: -- Best regards, Leo David

Since this is a single node gluster install, you have to add the gluster volume. Log into the HE web gui go to Storage, Storage Domains, click on "New Domain" (it's located at the top right side) Storage Type: select GlusterFS Export Path: enter in this format "myserver.mydomain.com:/my/local/path" Click ok Wait for it to do it's thing

No problem Leo. Glad it worked out ok!!

0) install ovirt node v4.2.3.1 (or higher) 1) Create a blacklist here: /etc/multiapth/conf.d/local.conf (assuming local.conf is the new file you create) 2) local.conf should be similar to this (using your disks wwid) blacklist { wwid INTEL_SSDSCKHB120G4_BTWM65160025120B wwid eui.0025385171b04d62 wwid SAMSUNG_MZ7GE960HMHP-000AZ_S1P8NYAG123827 } 3) remove multiapth device using multipath -f INTEL_SSDSCKHB120G4_BTWM65160025120B run this command: dracut --force --add multipath --include /etc/multipath /etc/multipath 4) Reboot 5) proceed with the rest of oVirt install