
I had the same issue with a new 3-node deploy on 4.4.8 [root@ovirt-node0 ~]# dnf list ovirt* Last metadata expiration check: 0:20:41 ago on Wed 15 Sep 2021 10:54:31 AM UTC. Installed Packages ovirt-ansible-collection.noarch 1.6.2-1.el8 @System ovirt-host.x86_64 4.4.8-1.el8 @System TASK [gluster.infra/roles/backend_setup : Set Gluster specific SeLinux context on the bricks] *** failed: [ovirt-node1] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sdb"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [ovirt-node0] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sdb"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [ovirt-node2] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sdb"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [ovirt-node1] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sdb"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [ovirt-node0] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sdb"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [ovirt-node2] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sdb"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [ovirt-node1] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sdb"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [ovirt-node0] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sdb"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [ovirt-node2] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sdb"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* ovirt-node0 : ok=52 changed=13 unreachable=0 failed=1 skipped=117 rescued=0 ignored=1 ovirt-node1 : ok=51 changed=12 unreachable=0 failed=1 skipped=117 rescued=0 ignored=1 ovirt-node2 : ok=51 changed=12 unreachable=0 failed=1 skipped=117 rescued=0 ignored=1 Please check /var/log/cockpit/ovirt-dashboard/gluster-deployment.log for more informations. Just to confirm: [root@ovirt-node0 ~]# semanage fcontext -a -t glusterd_brick_t "/gluster_bricks(/.*)?" ValueError: Type glusterd_brick_t is invalid, must be a file or device type [root@ovirt-node0 ~]#