Verified this BZ with # rpm -qa | grep gluster glusterfs-api-6.0-46.el8rhgs.x86_64 glusterfs-selinux-1.0-2.el8rhgs.noarch glusterfs-libs-6.0-46.el8rhgs.x86_64 glusterfs-client-xlators-6.0-46.el8rhgs.x86_64 glusterfs-fuse-6.0-46.el8rhgs.x86_64 python3-gluster-6.0-46.el8rhgs.x86_64 glusterfs-server-6.0-46.el8rhgs.x86_64 glusterfs-geo-replication-6.0-46.el8rhgs.x86_64 nfs-ganesha-gluster-2.7.3-15.el8rhgs.x86_64 glusterfs-6.0-46.el8rhgs.x86_64 glusterfs-cli-6.0-46.el8rhgs.x86_64 glusterfs-ganesha-6.0-46.el8rhgs.x86_64 Performed file locking test with brick down,server & client reboot scenarios.Have not observed these msgs in brick log while performing file locking test. However,will perform more locking related test in regression cycle to monitor these messages in QE testing as there are no concrete steps to verify this issue.Moving this BZ to verified state
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (glusterfs bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:5603