glusterfs: the nfs-ganesha driver displays wrong export location
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
High
|
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-
$
$ showmount -e 172.16.53.14
Export list for 172.16.53.14:
/share-
$ sudo mount -t nfs -o vers=4 root@172.
mount.nfs: Failed to resolve server root@172.16.53.14: No address associated with hostname
$
$ sudo mount -t nfs -o vers=4 172.16.
mount.nfs: access denied by server while mounting 172.16.
$
$ sudo mount -t nfs -o vers=4 172.16.
$ mount
172.16.
$
$
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,,
[root@]
when it actually should be,
<host-ip>
description: | updated |
description: | updated |
Changed in manila: | |
importance: | Undecided → High |
milestone: | none → liberty-rc1 |
Changed in manila: | |
status: | In Progress → Fix Committed |
Changed in manila: | |
status: | Fix Committed → Fix Released |
Changed in manila: | |
milestone: | liberty-rc1 → 1.0.0 |
Fix proposed to branch: master /review. openstack. org/224885
Review: https:/