glusterfs: the nfs-ganesha driver displays wrong export location

Bug #1493080 reported by Ramana Raja on 2015-09-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Csaba Henk

Bug Description

The glusterfs share driver that uses NFS Ganesha server to mediate access to the shares, displays the wrong export location.

$ manila list
ID | Name | Size | Share Proto | Status | Is Public | Share Type | Export location

dbeba93f-a1a1-4143-8602-c42162a00ab6 | None | 1 | NFS | available | False | glusterfs_ganesha | root@
$ showmount -e
Export list for

$ sudo mount -t nfs -o vers=4 root@ /mnt/nfsv4
mount.nfs: Failed to resolve server root@ No address associated with hostname
$ sudo mount -t nfs -o vers=4 /mnt/nfsv4
mount.nfs: access denied by server while mounting
$ sudo mount -t nfs -o vers=4 /mnt/nfsv4
$ mount on /mnt/nfsv4 type nfs

The actual NFS export location and the export location displayed using Manila CLI are not the same. The Manila command displays the export location with the following syntax,,
when it actually should be,

Ramana Raja (rraja) on 2015-09-07
description: updated
description: updated

Fix proposed to branch: master

Changed in manila:
assignee: nobody → Csaba Henk (chenk)
status: New → In Progress
Changed in manila:
importance: Undecided → High
milestone: none → liberty-rc1
Changed in manila:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2015-09-22
Changed in manila:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2015-10-15
Changed in manila:
milestone: liberty-rc1 → 1.0.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers