Hi Ritesh ,

I'm 90% confident it is a problem from the latest (4.3 to 4.4 ) or older migrations (4.2 to 4.3).

[root@ovirt2 ~]# ll /var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post
lrwxrwxrwx. 1 root root 64 9 яну 23,55 /var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post -> /usr/libexec/glusterfs/glusterfind/S57glusterfind-delete-post.py
[root@ovirt2 ~]# ll -Z /var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post
lrwxrwxrwx. 1 root root unconfined_u:object_r:glusterd_var_lib_t:s0 64 9 яну 23,55 /var/lib/glusterd/hooks/1/delete/post/S57glusterfind-delete-post -> /usr/libexec/glusterfs/glusterfind/S57glusterfind-delete-post.py
[root@ovirt2 ~]# ls -lZ /usr/libexec/glusterfs/glusterfind/S57glusterfind-delete-post.py
-rwxr-xr-x. 1 root root system_u:object_r:bin_t:s0 1883 12 окт 13,09 /usr/libexec/glusterfs/glusterfind/S57glusterfind-delete-post.py
[root@ovirt2 ~]# file /usr/libexec/glusterfs/glusterfind/S57glusterfind-delete-post.py
/usr/libexec/glusterfs/glusterfind/S57glusterfind-delete-post.py: Python script, ASCII text executable


I've tried with SELINUX in permissive mode, so it's something not related to SELINUX. Also the sync works on the new cluster.

Any idea how to debug it and find what is the reason it doesn't like it ?

Best Regards,
Strahil Nikolov