Description of problem: With Kilo branch of openstack, the export location for shares created from gluster-NFS-ganesha is incorrect. Currently the export location is of the format - <user>@<server-ip>:/<vol-name>-share-<share-id> Correct format of export location for NFSv3 shares should be - <server-ip>:/share-<share-id> and for NFSv4 shares - server-ip>:/share-<share-id>--<access-id> where, share-id is the id of manila share created access-id is the id created while 'access-allow' is performed for a particular share. This can be figured out by performing 'access-list' for a share Version-Release number of selected component (if applicable): # rpm -qa | grep 'manila' python-manila-2015.1.0-2.el7ost.noarch openstack-manila-2015.1.0-2.el7ost.noarch python-manilaclient-1.1.0-1.el7ost.noarch openstack-manila-share-2015.1.0-2.el7ost.noarch How reproducible: Always Steps to Reproduce: 1. Configure glusterfs driver for gluster-nfs-ganesha 2. create a share 3. List the shares to get export location Actual results: Export location - root@<hostip>:/gluster-nfs-ganesha-100G-02/share-50598280-a07d-4720-8ef8-0c4374722f00 Expected results: export location for NFSv3: 10.70.37.42:/share-50598280-a07d-4720-8ef8-0c4374722f00 export location for NFSv4: 10.70.37.42:/share-50598280-a07d-4720-8ef8-0c4374722f00--8fc01ce2-e020-41dd-92d6-138a5b54016c Additional info: [root@rhs-client20 ~(keystone_admin)]# manila access-list 50598280-a07d-4720-8ef8-0c4374722f00 +--------------------------------------+-------------+-------------+--------------+--------+ | id | access type | access to | access level | state | +--------------------------------------+-------------+-------------+--------------+--------+ | 8fc01ce2-e020-41dd-92d6-138a5b54016c | ip | 10.70.xx.xx | rw | active | +--------------------------------------+-------------+-------------+--------------+--------+
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.