Bug 1635683 - Setting the volume option using gluster ansible is failing
Summary: Setting the volume option using gluster ansible is failing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-ansible
Version: rhgs-3.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.4.z Batch Update 1
Assignee: Sachidananda Urs
QA Contact: SATHEESARAN
URL:
Whiteboard:
: 1635821 (view as bug list)
Depends On:
Blocks: 1635684
TreeView+ depends on / blocked
 
Reported: 2018-10-03 13:27 UTC by bipin
Modified: 2019-04-03 10:02 UTC (History)
7 users (show)

Fixed In Version: gluster-ansible-roles-1.0.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1635684 (view as bug list)
Environment:
Last Closed: 2018-10-31 08:42:30 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3428 0 None None None 2018-10-31 08:43:22 UTC

Description bipin 2018-10-03 13:27:29 UTC
Description of problem:
While setting the options for the gluster volume, the commands fails by throwing  an error that its not supported. The later commands works fine.

Snippet:
=======
TASK [gluster.features/roles/gluster_hci : Create the GlusterFS volumes] ******************************************************************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: None
failed: [rhsqa-grafton6.lab.eng.blr.redhat.com] (item={u'volname': u'engine', u'brick': u'/gluster_bricks/engine/engine'}) => {"changed": false, "item": {"brick": "/gluster_bricks/engine/engine", "volname": "engine"}, "msg": "error running gluster (/usr/sbin/gluster --mode=script volume set engine cluster.granular-entry-heal enable) command (rc=1): volume set: failed:  'gluster volume set <VOLNAME> cluster.granular-entry-heal {enable, disable}' is not supported. Use 'gluster volume heal <VOLNAME> granular-entry-heal {enable, disable}' instead.\n"}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: None
failed: [rhsqa-grafton6.lab.eng.blr.redhat.com] (item={u'volname': u'data', u'brick': u'/gluster_bricks/data/data'}) => {"changed": false, "item": {"brick": "/gluster_bricks/data/data", "volname": "data"}, "msg": "error running gluster (/usr/sbin/gluster --mode=script volume set data cluster.granular-entry-heal enable) command (rc=1): volume set: failed:  'gluster volume set <VOLNAME> cluster.granular-entry-heal {enable, disable}' is not supported. Use 'gluster volume heal <VOLNAME> granular-entry-heal {enable, disable}' instead.\n"}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: None
failed: [rhsqa-grafton6.lab.eng.blr.redhat.com] (item={u'volname': u'vmstore', u'brick': u'/gluster_bricks/vmstore/vmstore'}) => {"changed": false, "item": {"brick": "/gluster_bricks/vmstore/vmstore", "volname": "vmstore"}, "msg": "error running gluster (/usr/sbin/gluster --mode=script volume set vmstore cluster.granular-entry-heal enable) command (rc=1): volume set: failed:  'gluster volume set <VOLNAME> cluster.granular-entry-heal {enable, disable}' is not supported. Use 'gluster volume heal <VOLNAME> granular-entry-heal {enable, disable}' instead.\n"}




Version-Release number of selected component (if applicable):
gluster-ansible-roles-1.0.2-2.el7rhgs.noarch

How reproducible:
Always

Steps to Reproduce:
1.Create a playbook to deploy RHHI enviornment
2.Throws error while enabling cluster entry heal volume option


Actual results:
Fails while enabling the options

Expected results:
Should use the later command 

Additional info:

Comment 2 SATHEESARAN 2018-10-04 02:52:40 UTC
*** Bug 1635821 has been marked as a duplicate of this bug. ***

Comment 4 SATHEESARAN 2018-10-16 02:38:48 UTC
Tested with gluster-ansible-roles-1.0.3

Volume set option 'granular-entry-heal' is not longer set via gluster volume set option.

Comment 6 errata-xmlrpc 2018-10-31 08:42:30 UTC
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-2018:3428


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