glusterfs_driver: Access-deny for glusterfs driver should be dynamic
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Shared File Systems Service (Manila) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Description of problem:
With Kilo branch of openstack, Even after we deny access to a gluster-NFS share, IO is allowed to existing mounts. Any new attempt to mount is denied access though. To be more effective, we should cease access to share immediately after access is denied even on existing mounts.
Version-Release number of selected component (if applicable):
# rpm -qa | grep 'manila'
python-
openstack-
python-
openstack-
How reproducible:
Always
Steps to Reproduce:
1. configure manila.conf to use gluster-nfs server
2. create a gluster-nfs share using manila
3. Allow access to this share to a nova VM
4. mount the share and run IO
5. For the share created in step 2, Deny access to the nova VM
6. IO still continues
Actual results:
After we deny access to a gluster-nfs share,
- IO continues on existing mounts
- Any attempt to mount the share fails
Expected results:
After we deny access to a gluster-nfs share,
- IO to existing mount should be ceased immediately
