[Bugs] [Bug 1251857] nfs-ganesha: new volume creation tries to bring up glusterfs-nfs even when nfs-ganesha is already on

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1251857



--- Comment #1 from Meghana <mmadhusu at redhat.com> ---
Once we have nfs-ganesha up and running, the new volume creation still tries to
bring up the glusterfs-nfs up, though unsuccessfully.

This is visible once you check the gluster status for that particular newly
created volume,

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


How reproducible:
always

Steps to Reproduce:
1. create a volume of type 6x2, start it
2. bring up nfs-ganesha, after doing all the pre-requisites
3. create another volume of any type,
4. gluster volume status <name of newly created volume>

Actual results:
step 4 results in response as displayed in description section

Expected results:
we should have a mechanism to find out if nfs-ganesha is already running, then
the new volume should accept that as the nfs server, rather try to bring
glusterfs-nfs.

-- 
You are receiving this mail because:
You are the assignee for the bug.