Hello List, Recently I had upgraded my oVirt + Gluster (v6.5 -> v6.6) and I hit an ACL bug , which forced me to upgrade to v7.0 Another oVirt user also hit the bug when upgrading to v6.7 and he had to rebuild his gluster cluster. Sadly, the fun doesn't stop here. Last week I have tried upgrading to v7.2 and again the ACL bug hit me. Downgrading to v7.1 doesn't help - so I downgraded to 7.0 and everything is operational. The bug report for the last issue: https://bugzilla.redhat.com/show_bug.cgi?id=1797099 I have 2 questions : 1. What is gluster's ACL evaluating/checking ? Is there an option to force gluster not to support ACL at all ? 2. Are you aware of the issue? That bug was supposed to be fixed a long time ago, yet the facts speak different. Thanks for reading this long post. Best Regards, Strahil Nikolov _______________________________________________ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/441850968 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/441850968 Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
