Fix GaneshaNASHelper update_access signature

The gluster GaneshaNFSHelper update_access method calls
into the GaneshaNASHelper update_access method, but the
signature it uses for this call is not up to date with
the 2017 dynamic export changes made to the Ganesha
driver.

Fix this by adding an update_access method to
the gluster-specific GaneshaNFSHelper which accepts
the signature that the Gluster driver expects but calls
into Ganesha with the signature that it expects.

[1] Change-Id: I01ec100c0afe28a84e9afa8e0660d299e4b3d160

Closes-Bug: #1964696
Change-Id: I2cae5ba54ae0a95e84d5ef7cf0f05287b7ae5d22
(cherry picked from commit 6f4191a6d9)

manila/share/drivers/glusterfs/__init__.py

@@ -309,3 +309,13 @@ class GaneshaNFSHelper(ganesha.GaneshaNASHelper):
         return {"Hostname": self.gluster_manager.host,
                 "Volume": self.gluster_manager.volume,
                 "Volpath": self.gluster_manager.path}
+
+    def update_access(self, base_path, share, add_rules, delete_rules,
+                      recovery=False):
+        """Update access rules."""
+
+        context = None
+        access_rules = []
+        super(GaneshaNFSHelper, self).update_access(
+            context, share, access_rules, add_rules,
+            delete_rules, share_server=None)

releasenotes/notes/bug-1964696-fix-GaneshaNFSHelper-update_access-6124a79e34e63030.yaml

@@ -0,0 +1,7 @@
+---
+fixes:
+  - |
+    `Bug #1964696 <https://bugs.launchpad.net/manila/+bug/1964696>`_: Fix
+    calling the GaneshaNASHelper `update_access` method from the gluster
+    GaneshaNFSHelper with the wrong signature.
+