[ovirt-users] Re: New failure Gluster deploy: Set granual-entry-heal on --> Bricks down

Still not able to deploy Gluster on oVirt Node Hyperconverged - same error; upgraded to v4.4.4 and "kvdo not installed" Tried suggestion and per https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.5... I also tried "gluster volume heal VOLNAME granular-entry-heal enable" then "gluster volume heal VOLNAME" received "transport endpoint is not connected" double checked networking, restarted the volume per https://access.redhat.com/solutions/5089741 using "gluster volume start VOLNAME force" also checked Gluster server and client versions per https://access.redhat.com/solutions/5380531 --> self-heal daemon shows process ID and local status but not peer status updated to oVirt v4.4.4 and now am receiving "vdo: ERROR - Kernel module kvdo not installed\nvdo: ERROR - modprobe: FATAL: Module kvdo not found in directory /lib/modules/4.18.0-240.1.1.el8_3.x86_64\n" This appears to be a recent issue. I am going to re-image nodes with oVirt Node v4.4.4 and rebuild networking and see if that helps, if not I will revert to v4.4.2 (most recent successful on this cluster) and see if I can build it there. I am using local direct cable between three host nodes for storage network, with statically assigned IPs on local network adapters along with Hosts file and 3x /30 subnets for routing. Management network is DHCP and set up as before when successful. I have confirmed "files" is listed first in nsswitch.conf and have not had any issues with ssh to storage network or management network --> could anything related to direct cabling be reason for peer connection issue with self-heal daemon even though "gluster peer status" and "gluster peer probe" are successful? Thanks again, I will update after rebuilding with oVirt Node v4.4.4 Respectfully, Charles