Bug 1272960 - glusterfs_driver: Glusterfs NFS-Ganesha share's export location should be uniform for both nfsv3 & nfsv4 protocols
glusterfs_driver: Glusterfs NFS-Ganesha share's export location should be uni...
Product: RDO
Classification: Community
Component: openstack-manila (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: Kilo
Assigned To: Pete Zaitcev
Depends On:
  Show dependency treegraph
Reported: 2015-10-19 06:09 EDT by krishnaram Karthick
Modified: 2016-05-19 11:32 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:32:54 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-10-19 06:09:33 EDT
Description of problem:

In Liberty, export location for gluster nfs-ganesha is different for nfsv3 & nfsv4 protocols.

NFSv3 share location is of the format - <ganesha server ip>:/<share-id> and NFSv4 share location is of the format - <ganesha server ip>:/<share-id>--<access-id>.

Export location listed in 'manila list' works only with NFSv3 protocol. Using same path to export share using NFSv4 protocol fails.

cropped output of 'manila list' command:

|ID| Name| export location|
| 7303bc3d-bb1f-4d7b-9171-0c168edcc78c | nfs-ganesha-vol10 |

Version-Release number of selected component (if applicable):

# rpm -qa | grep 'manila'

How reproducible:

Steps to Reproduce:
create a share and using the export location attempt to mount the share using nfsV4 proocol

Actual results:
export location is invalid

Expected results:
A valid export location should be available

Additional info:
Export location for both nfsv3 and nfsv4 should use pseudo path i.e., <ganesha server ip>:/<share-id>--<access-id>
Comment 1 Chandan Kumar 2016-05-19 11:32:54 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.