When setting up over the UI, last step shows the ansible tasks. Can you find your version of and print it here: Set Gluster specific SeLinux context on the bricks' Best Regards,Strahil Nikolov On Wed, Sep 8, 2021 at 12:43, dhanaraj.ramesh--- via Users<users(a)ovirt.org> wrote: Hi  Team I'm trying to setup 3 node Gluster + ovirt  setup with latest stable 4.4.8 version but while deploying the gluster from cokpit getting below error what could be the reason TASK [gluster.infra/roles/backend_setup : Set Gluster specific SeLinux context on the bricks] *** failed: [beclovkvma03.bec. lab ] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma01.bec. lab ] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma02.bec. lab ] (item={'path': '/gluster_bricks/engine', 'lvname': 'gluster_lv_engine', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma03.bec. lab ] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma01.bec. lab ] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma02.bec. lab ] (item={'path': '/gluster_bricks/data', 'lvname': 'gluster_lv_data', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_data", "path": "/gluster_bricks/data", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma03.bec. lab ] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma01.bec. lab ] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sde"}, "msg": "ValueError: Type glusterd_brick_t is invalid, must be a file or device type\n"} failed: [beclovkvma02.bec. lab ] (item={'path': '/gluster_bricks/vmstore', 'lvname': 'gluster_lv_vmstore', 'vgname': 'gluster_vg_sde'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_vmstore", "path": "/gluster_bricks/vmstore", "vgname": "gluster_vg_sde"}, "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 ********************************************************************* beclovkvma01.bec. lab  : ok=53  changed=14  unreachable=0    failed=1    skipped=116  rescued=0    ignored=1  beclovkvma02.bec. lab  : ok=52  changed=13  unreachable=0    failed=1    skipped=116  rescued=0    ignored=1  beclovkvma03.bec. lab  : ok=52  changed=13  unreachable=0    failed=1    skipped=116  rescued=0    ignored=1  _______________________________________________ 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/HXKAQXCVQ24...

I think that in the UI there is an option to edit.Find and replace glusterd_brick_t with system_u:object_r:glusterd_brick_t:s0 and run again. Best Regards,Strahil Nikolov On Thu, Sep 16, 2021 at 12:33, bgriffis@affinityplus.org<bgriffis(a)affinityplus.org> wrote: 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 ~]# _______________________________________________ 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/OAZY67QM347...

It should be   system_u:object_r:glusterd_brick_t:s0 Best Regards,Strahil Nikolov I'm having this same issue on 4.4.8 with a fresh 3-node install as well. Same errors as the OP.  Potentially relevant test command: [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 Seems like the glusterd selinux fcontexts are missing.  Are they provided by glusterd_selinux? [root@ovirt-node0 ~]# dnf install selinux-policy Last metadata expiration check: 0:03:51 ago on Wed 15 Sep 2021 11:31:59 AM UTC. Package selinux-policy-3.14.3-79.el8.noarch is already installed. _______________________________________________ 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/SSSS7KJYS43...

Hi, the bug states that has been done because glusterfs includes it's own selinux policy module. So maybe ovirt-host needs a dependency to glusterfs-selinux ? Greetings Klaas On 10/7/21 01:04, jinyx007(a)gmail.com wrote: > I've been having the same issue and I barely have any hair left. I did find something though; per selinux-policy changelog: > > https://centos.pkgs.org/8-stream/centos-baseos-aarch64/selinux-policy-3.1... > > 2021-08-12 - Zdenek Pytela <zpytela(a)redhat.com&gt; - 3.14.3-77 > ... > - Remove glusterd SELinux module from distribution policy > Resolves: rhbz#1816718 > > selinux-policy no longer contains gluster module thats why the policy can't be found. oVirt node iso is based in Stream which is up to date. Installing on a CentOS 8 or Almalinux/Rocky distro still uses the older *-67 so applying glusterfs selinux policy works fine. This issue deals with node iso. > _______________________________________________ > 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/CSTF7XZ2RJP...

I have the same issue. I am trying to figure out where you want me to make the change. You said in the ui, but I can see where. Can you help please, Thanks Brad

It was later discovered that the selinux policy was removed from the selinux packages. You will need gluster-selinux which should be available in the latest version of oVirt. Best Regards,Strahil Nikolov On Wed, Oct 20, 2021 at 3:17, admin@foundryserver.com&lt;admin(a)foundryserver.com&gt; wrote: I have the same issue.  I am trying to figure out where you want me to make the change.  You said in the ui, but I can see where. Can you help please, Thanks Brad _______________________________________________ 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/ZABW725GVWM...