Bug 1277792 - glusterfs_driver: Access-deny for glusterfs driver should be dynamic
glusterfs_driver: Access-deny for glusterfs driver should be dynamic
Product: RDO
Classification: Community
Component: openstack-manila (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: Kilo
Assigned To: Pete Zaitcev
Depends On:
  Show dependency treegraph
Reported: 2015-11-03 23:58 EST by krishnaram Karthick
Modified: 2016-05-19 11:58 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-05-19 11:58:44 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description krishnaram Karthick 2015-11-03 23:58:08 EST
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'

How reproducible:

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

Additional info:
Comment 1 Chandan Kumar 2016-05-19 11:58:44 EDT
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.

Note You need to log in before you can comment on or make changes to this bug.