So what's the conclusion on this bug? Did we manage to hit this again in the regression cycle? If not, any particular reason why this bug needs to be kept open? If this is constantly reproducible on VMs have we checked if the resource footprint for the same are according to the standard requirements of RHGS?
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-2021:1462
Comment 47Red Hat Bugzilla
2023-09-15 00:08:07 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days