[ovirt-users] Re: Scale out ovirt 4.3 (from 3 to 6 or 9 nodes) with hyperconverged setup and Gluster

On Tue, May 21, 2019 at 12:16 PM Sahina Bose <sabose(a)redhat.com&gt; wrote: > > > On Mon, May 20, 2019 at 9:55 PM Adrian Quintero <adrianquintero(a)gmail.com&gt; > wrote: > >> Sahina, >> Yesterday I started with a fresh install, I completely wiped clean all >> the disks, recreated the arrays from within my controller of our DL380 Gen >> 9's. >> >> OS: RAID 1 (2x600GB HDDs): /dev/sda // Using ovirt node 4.3.3.1 iso. >> engine and VMSTORE1: JBOD (1x3TB HDD):/dev/sdb >> DATA1: JBOD (1x3TB HDD): /dev/sdc >> DATA2: JBOD (1x3TB HDD): /dev/sdd >> Caching disk: JOBD (1x440GB SDD): /dev/sde >> >> *After the OS install on the first 3 servers and setting up ssh keys, I >> started the Hyperconverged deploy process:* >> 1.-Logged int to the first server http://host1.example.com:9090 >> 2.-Selected Hyperconverged, clicked on "Run Gluster Wizard" >> 3.-Followed the wizard steps (Hosts, FQDNs, Packages, Volumes, Bricks, >> Review) >> *Hosts/FQDNs:* >> host1.example.com >> host2.example.com >> host3.example.com >> *Packages:* >> *Volumes:* >> engine:replicate:/gluster_bricks/engine/engine >> vmstore1:replicate:/gluster_bricks/vmstore1/vmstore1 >> data1:replicate:/gluster_bricks/data1/data1 >> data2:replicate:/gluster_bricks/data2/data2 >> *Bricks:* >> engine:/dev/sdb:100GB:/gluster_bricks/engine >> vmstore1:/dev/sdb:2600GB:/gluster_bricks/vmstrore1 >> data1:/dev/sdc:2700GB:/gluster_bricks/data1 >> data2:/dev/sdd:2700GB:/gluster_bricks/data2 >> LV Cache: >> /dev/sde:400GB:writethrough >> 4.-After I hit deploy on the last step of the "Wizard" that is when I >> get the disk filter error. >> TASK [gluster.infra/roles/backend_setup : Create volume groups] >> **************** >> failed: [vmm10.virt.iad3p] (item={u'vgname': u'gluster_vg_sdb', >> u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " Device /dev/sdb >> excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": >> "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", >> "rc": 5} >> failed: [vmm12.virt.iad3p] (item={u'vgname': u'gluster_vg_sdb', >> u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " Device /dev/sdb >> excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": >> "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", >> "rc": 5} >> failed: [vmm11.virt.iad3p] (item={u'vgname': u'gluster_vg_sdb', >> u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " Device /dev/sdb >> excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": >> "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", >> "rc": 5} >> failed: [vmm12.virt.iad3p] (item={u'vgname': u'gluster_vg_sdc', >> u'pvname': u'/dev/sdc'}) => {"changed": false, "err": " Device /dev/sdc >> excluded by a filter.\n", "item": {"pvname": "/dev/sdc", "vgname": >> "gluster_vg_sdc"}, "msg": "Creating physical volume '/dev/sdc' failed", >> "rc": 5} >> failed: [vmm10.virt.iad3p] (item={u'vgname': u'gluster_vg_sdc', >> u'pvname': u'/dev/sdc'}) => {"changed": false, "err": " Device /dev/sdc >> excluded by a filter.\n", "item": {"pvname": "/dev/sdc", "vgname": >> "gluster_vg_sdc"}, "msg": "Creating physical volume '/dev/sdc' failed", >> "rc": 5} >> failed: [vmm11.virt.iad3p] (item={u'vgname': u'gluster_vg_sdc', >> u'pvname': u'/dev/sdc'}) => {"changed": false, "err": " Device /dev/sdc >> excluded by a filter.\n", "item": {"pvname": "/dev/sdc", "vgname": >> "gluster_vg_sdc"}, "msg": "Creating physical volume '/dev/sdc' failed", >> "rc": 5} >> failed: [vmm10.virt.iad3p] (item={u'vgname': u'gluster_vg_sdd', >> u'pvname': u'/dev/sdd'}) => {"changed": false, "err": " Device /dev/sdd >> excluded by a filter.\n", "item": {"pvname": "/dev/sdd", "vgname": >> "gluster_vg_sdd"}, "msg": "Creating physical volume '/dev/sdd' failed", >> "rc": 5} >> failed: [vmm12.virt.iad3p] (item={u'vgname': u'gluster_vg_sdd', >> u'pvname': u'/dev/sdd'}) => {"changed": false, "err": " Device /dev/sdd >> excluded by a filter.\n", "item": {"pvname": "/dev/sdd", "vgname": >> "gluster_vg_sdd"}, "msg": "Creating physical volume '/dev/sdd' failed", >> "rc": 5} >> failed: [vmm11.virt.iad3p] (item={u'vgname': u'gluster_vg_sdd', >> u'pvname': u'/dev/sdd'}) => {"changed": false, "err": " Device /dev/sdd >> excluded by a filter.\n", "item": {"pvname": "/dev/sdd", "vgname": >> "gluster_vg_sdd"}, "msg": "Creating physical volume '/dev/sdd' failed", >> "rc": 5} >> >> Attached is the generated yml file ( /etc/ansible/hc_wizard_inventory.yml) >> and the "Deployment Failed" file >> >> >> >> >> Also wondering if I hit this bug? >> https://bugzilla.redhat.com/show_bug.cgi?id=1635614 >> >> > +Sachidananda URS <surs(a)redhat.com&gt; +Gobinda Das <godas(a)redhat.com&gt; to > review the inventory file and failures > Hello Adrian, Can you please provide the output of: # fdisk -l /dev/sdd # fdisk -l /dev/sdb I think there could be stale signature on the disk causing this error. Some of the possible solutions to try: 1) # wipefs -a /dev/sdb # wipefs -a /dev/sdd 2) You can zero out first few sectors of disk by: # dd if=/dev/zero of=/dev/sdb bs=1M count=10 3) Check if partition is visible in /proc/partitions If not: # partprobe /dev/sdb 4) Check if filtering is configured wrongly in /etc/lvm/lvm.conf grep for 'filter =' -sac