Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1394796 - gdeploy: Volname should be made optional in nfs-ganesha create-cluster
gdeploy: Volname should be made optional in nfs-ganesha create-cluster
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gdeploy (Show other bugs)
3.2
x86_64 Linux
unspecified Severity medium
: ---
: RHGS 3.3.0
Assigned To: Sachidananda Urs
Manisha Saini
:
Depends On:
Blocks: 1417147
  Show dependency treegraph
 
Reported: 2016-11-14 08:17 EST by Arthy Loganathan
Modified: 2017-09-21 00:49 EDT (History)
11 users (show)

See Also:
Fixed In Version: gdeploy-2.0.1-2
Doc Type: Enhancement
Doc Text:
With this release, ‘volname’ is made optional while creating NFS Ganesha cluster, which was mandatory before. You might want to create a NFS Ganesha cluster without exporting or building any volumes i.e. creating a cluster without having any gluster volume.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-09-21 00:49:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2777 normal SHIPPED_LIVE gdeploy bug fix and enhancement update for RHEL7 2017-09-21 04:23:08 EDT

  None (edit)
Description Arthy Loganathan 2016-11-14 08:17:18 EST
Description of problem:
User can setup ganesha without having any volumes and later they can create and export volumes. Hence, volname should be made optional in nfs-ganesha create-cluster.

Version-Release number of selected component (if applicable):
gdeploy-2.0.1-3.el7rhgs.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create nfs.ganesha.conf without 'volname' key in create-cluster.
2. Run gdeploy for setting up ganesha.

Actual results:
Ganesha cluster creation succeeds, but it also tries to export volume which is undefined in conf file and it fails.

Expected results:
Ganesha cluster creation should succeed without any error.

Additional info:

Error Message:

TASK [Exports/Unexports volume through NFS-Ganesha] ****************************
fatal: [dhcp46-111.lab.eng.blr.redhat.com]: FAILED! => {"failed": true, "msg": "the field 'args' has an invalid value, which appears to include a variable that is undefined. The error was: 'volname' is undefined\n\nThe error appears to have been in '/tmp/tmpI5Ra8w/gluster-volume-export-ganesha.yml': line 7, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n  tasks:\n    - name: Exports/Unexports volume through NFS-Ganesha\n      ^ here\n"}
to retry, use:
                --limit
                @/tmp/tmpI5Ra8w/gluster-volume-export-ganesha.retry
Comment 2 Sachidananda Urs 2016-11-14 10:01:13 EST
Since this is not a blocker, and very minimal use case of someone setting up NFS Ganesha without a volume I suggest that we move this beyond 3.2.0.

Arthy hope that is fine.
Comment 3 Arthy Loganathan 2016-11-16 01:56:10 EST
Discussed with Alok and since this is very minimal use case, we move this beyond 3.2.0
Comment 5 Sachidananda Urs 2017-02-27 03:15:13 EST
Commit: https://github.com/gluster/gdeploy/commit/42fecd22 fixes the issue.
Comment 7 Manisha Saini 2017-04-28 05:15:43 EDT
Verified this bug on gdeploy-2.0.2-4.el7rhgs.noarch

Ganesha cluster creation succeed without giving volume name under [nfs-ganesha] section in gdeploy.No errors related to volume export were observed.

Moving it to verified state
Comment 11 errata-xmlrpc 2017-09-21 00:49:50 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2777

Note You need to log in before you can comment on or make changes to this bug.