Bug 1693187

Summary:	"Volume Option cluster.granular-entry-heal=enable could not be set" when using "Optimize for Virt store"
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	rhhi	Assignee:	Kaustav Majumder <kmajumde>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	low	Docs Contact:
Priority:	high
Version:	rhhiv-1.6	CC:	godas, kmajumde, pasik, rhs-bugs, sabose
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHHI-V 1.8
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1673277	Environment:
Last Closed:	2020-08-04 14:50:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1673277
Bug Blocks:	1779975

Description SATHEESARAN 2019-03-27 10:08:08 UTC

Description
-----------
When I use "Optimize for Virt store" on one of our newly created storage volumes, I get one option that failed: 

2019-02-06 10:25:02,353+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-15727) [051cfc8c-9efc-427c-9e2e-9127e3e0a86d] EVENT_ID: GLUSTER_VOLUME_OPTION_SET_FAILED(4,003), Volume Option cluster.granular-entry-heal=enable could not be set on ssd9 of cluster GlusterFS-storage.


This looks like the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1635684

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

When the option is already set, it reports ok.

Comment 1 SATHEESARAN 2019-07-18 18:39:52 UTC

The dependent ovirt bug is targeted for ovirt-4.3.6

Comment 2 SATHEESARAN 2019-09-04 01:18:30 UTC

Tested with vdsm-4.30.29

Still hit the problem, looks like the code path still uses 'volume set'.


The behavior as observed:
1. When volume is just created, 'optimize for virt-store' works
2. When the volume is started, 'optimize for virt-store' fails.


Expectation:
At any stage of volume: created, started, or stopped, volume set operation should not throw any error
In this case, it fails for 'granular-entry-heal'


Information
Replica 3 volume when set with 'granular-entry-heal' during 'optimize for virtstore',
should do check for some conditions:

1. When the volume is just created, use 'gluster volume set' to be used
2. Once the volume is in stopped or started state, 'gluster volume heal' command to be used

Comment 3 SATHEESARAN 2019-09-04 07:28:59 UTC

This bug needs fix that will be addressed with patch from Kaustav. ( As we discussed in Google chat platform )
This bug is not a blocker as all the volume options are set through gluster-ansible for deployment.
This issue affects only the customers that try to optimize volume ( that is already started ) for virt store from RHV Manager UI.

Considering this, the impact/severity is low in this case
Re-targeting this bug for RHV 4.3.7

Comment 5 SATHEESARAN 2020-06-17 02:52:48 UTC

Tested with RHV Manager 4.4.1.2-0.10.el8ev and vdsm-4.40.20-1.el8ev.x86_64

1. When volume is just created, 'optimize for vmstore' from RHV Manager Admin portal enables granular-entry-heal
2. When volume is started once, 'optimize for vmstore' from RHV Manager Admin portal fails to set granular-entry-heal,
but the value is set with 'gluster volume heal' command

Comment 8 errata-xmlrpc 2020-08-04 14:50:55 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 (RHHI for Virtualization 1.8 bug fix and enhancement update), 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/RHEA-2020:3314