Bug 1123052 - [HC] Validate glusterfs volume parameters required for ovirt storage domains
Summary: [HC] Validate glusterfs volume parameters required for ovirt storage domains
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Ala Hino
QA Contact: Elad
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-24 17:57 UTC by Federico Simoncelli
Modified: 2016-03-09 19:23 UTC (History)
15 users (show)

Fixed In Version: v4.17.0.8
Doc Type: Bug Fix
Doc Text:
Red Hat recommends using glusterfs volumes that are replica type and replica count 1 or 3. Previously, VDSM did not validate glusterfs volumes when adding glusterfs storage domains. As a result, administrators could configure glusterfs volumes with an unsupported replica type and count. VDSM now validates the required parameters before using a glusterfs volume as a storage domain, and if the glusterfs volume configuration is not supported, there is a warning.
Clone Of:
Last Closed: 2016-03-09 19:23:35 UTC
oVirt Team: Storage
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0362 0 normal SHIPPED_LIVE vdsm 3.6.0 bug fix and enhancement update 2016-03-09 23:49:32 UTC
oVirt gerrit 31041 0 None None None Never
oVirt gerrit 41931 0 master MERGED gluster: Verify volume is Replica 3 Never

Description Federico Simoncelli 2014-07-24 17:57:30 UTC
Description of problem:
VDSM should validate all the required parameters before using a gluster volume as a storage domain.

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

Additional info:

Comment 1 Allon Mureinik 2014-07-25 07:51:31 UTC
Sahina, your team or mine?

Comment 2 Sahina Bose 2014-07-30 14:00:23 UTC
(In reply to Allon Mureinik from comment #1)
> Sahina, your team or mine?

Allon, I think the check for if the options are present could be done by the storage team.

We could set the options on the volume as part of the "Optimize for virt store" option available on the volume - this can be done by the gluster team

Comment 3 Allon Mureinik 2014-09-03 08:36:23 UTC
Anmol, does your patch referenced in the BZ solve the issue, or is there anything else that should be done here?

Comment 4 anmol babu 2014-09-03 09:58:38 UTC
My patch 
1. Checks if the volume is of the recommended configuration :
   a. If no, issues a warning just in case if it is not.However the user can still go ahead and optimise the volume for virt store in which case the UI enables the required options if the volume is of replicate type.
   b. If yes, optimise for virt store.

So in all, the patch is a UI patch with validation + options setting handled from UI.

(In reply to Allon Mureinik from comment #3)
> Anmol, does your patch referenced in the BZ solve the issue, or is there
> anything else that should be done here?

Comment 5 Tal Nisan 2014-09-29 16:03:11 UTC
So after this patch, what are we currently missing in order to close this bug?

Comment 6 anmol babu 2014-10-27 11:17:48 UTC
Firstly,My sincere apologies for a very delayed response. 
I don't think we are missing anything now as the required options are being set directly from UI and the additional options required are being handled from UI in the attached patch set upstream.And the new options are optional in the sense the user can choose to force optimise thereby overriding/ignoring the suggested configuration.

Comment 7 Tal Nisan 2014-10-28 14:23:26 UTC
Federico, this satisfies us?

Comment 8 Federico Simoncelli 2014-12-01 09:54:25 UTC
(In reply to Tal Nisan from comment #7)
> Federico, this satisfies us?

No, this RFE was filed to validate the parameters in VDSM when it's creating/connecting/using the Gluster Storage Domain.

Comment 9 Allon Mureinik 2015-05-31 13:30:15 UTC
Ala, I think you can take care of this as part of your re-working of gluster mounting.

Comment 10 Allon Mureinik 2015-06-29 19:17:08 UTC
Ala, please add some doctext explaining this feature.

Comment 14 Allon Mureinik 2015-08-10 08:43:38 UTC
Ala, please add the appropriate doctext.
Note that according to bug 1238093, we also support replica count of 1 (which was introduced a tad later, and isn't visible in the patches attached to this bug).

Comment 15 Elad 2015-10-12 09:49:47 UTC
VDSM validates that the Gluster volume resides on 1 or 3 bricks while using replica as expected. If a 2 bricks volume is given, the operation is aborted by VDSM with a UnsupportedGlusterVolumeReplicaCountError but engine doesn't know how to handle with it and fails with a NullPointerException: https://bugzilla.redhat.com/show_bug.cgi?id=1270732.
In case a distributed volume is provided for the domain, the operation is allowed and the domain is created successfully (tried with distributed 2 and 3)

I tested also with replica 6 and the results are the same as replica 2.

Tested using:

Comment 16 Ala Hino 2015-12-17 16:54:07 UTC
Behavior here changed per bug 1286565. Hence, doctext changed accordingly, i.e. if volume replica is not supported, there is a warning in the log instead of failing the operation.

Comment 18 errata-xmlrpc 2016-03-09 19:23:35 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.


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