Description of problem: During hyperconverged HE ansible gdeploy from cockpit, the gluster arbiter brick is being created on 2nd host, while the arbiter LV is created on the 3rd host. This happens during subsequent gluster volume creation from cockpit as well. VDO is not used in any of the attempts so far. It seems to be similar symptoms to these reports here - https://bugzilla.redhat.com/show_bug.cgi?id=1596523 https://bugzilla.redhat.com/show_bug.cgi?id=1596520 ------ Version-Release number of selected component (if applicable): ovirt-host-4.3.1-1.el7.x86_64 cockpit-ovirt-dashboard-0.12.3-1.el7.noarch ------ How reproducible: Happens every time a arbiter volume is created by gdeploy. ------ Steps to Reproduce: 1.Create a 3 replica arbiter volume with gdeploy 2.Use lsblk to check LV size 3.Use gluster volume info to check arbiter brick placement ------ Actual results: The gluster arbiter brick is being created on 2nd host, while the arbiter LV is created on the 3rd host. ------ Expected results: The gluster arbiter brick and LV is created on the third host. ------ Additional info: gluster volume info data1 Volume Name: data1 Type: Replicate Volume ID: 278655c7-ad7a-4637-9807-6db524551e2e Status: Started Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: fmt2-nde1.stor.diginode.net:/gluster_bricks/data1/data1 Brick2: fmt2-nde3.stor.diginode.net:/gluster_bricks/data1/data1 Brick3: fmt2-nde2.stor.diginode.net:/gluster_bricks/data1/data1 (arbiter) lsblk output: nde1: └─md101 9:101 0 431.8G 0 raid1 ├─gluster_vg_md101-gluster_lv_engine 253:2 0 80G 0 lvm /gluster_bricks/engine ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tmeta 253:3 0 4M 0 lvm │ └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm │ ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm │ └─gluster_vg_md101-gluster_lv_data1 253:7 0 330G 0 lvm /gluster_bricks/data1 └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tdata 253:4 0 351.8G 0 lvm └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm └─gluster_vg_md101-gluster_lv_data1 253:7 0 330G 0 lvm /gluster_bricks/data1 nde2: └─md101 9:101 0 431.8G 0 raid1 ├─gluster_vg_md101-gluster_lv_engine 253:2 0 80G 0 lvm /gluster_bricks/engine ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tmeta 253:3 0 4M 0 lvm │ └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm │ ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm │ └─gluster_vg_md101-gluster_lv_data1 253:7 0 330G 0 lvm /gluster_bricks/data1 └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tdata 253:4 0 351.8G 0 lvm └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm └─gluster_vg_md101-gluster_lv_data1 253:7 0 330G 0 lvm /gluster_bricks/data1 nde3: └─md101 9:101 0 431.8G 0 raid1 ├─gluster_vg_md101-gluster_lv_engine 253:2 0 80G 0 lvm /gluster_bricks/engine ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tmeta 253:3 0 4M 0 lvm │ └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm │ ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm │ └─gluster_vg_md101-gluster_lv_data1 253:7 0 20G 0 lvm /gluster_bricks/data1 └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101_tdata 253:4 0 351.8G 0 lvm └─gluster_vg_md101-gluster_thinpool_gluster_vg_md101-tpool 253:5 0 351.8G 0 lvm ├─gluster_vg_md101-gluster_thinpool_gluster_vg_md101 253:6 0 351.8G 0 lvm └─gluster_vg_md101-gluster_lv_data1 253:7 0 20G 0 lvm /gluster_bricks/data1
*** This bug has been marked as a duplicate of bug 1697965 ***