Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1429349

Summary: [RFE] Enable 'Optimize for Virt Store' by default, while creating the gluster volume
Product: [oVirt] ovirt-engine Reporter: SATHEESARAN <sasundar>
Component: BLL.GlusterAssignee: Sahina Bose <sabose>
Status: CLOSED DUPLICATE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: bugs, sasundar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-09 05:20:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description SATHEESARAN 2017-03-06 07:50:00 UTC 
Description of problem:
-----------------------
While creating the gluster volume from RHV UI, volume create dialog has the checkbox 'Optimize of Virt Store' which is not checked by default, which would lead to the volume created with not all the required volume options set.

When this volume is used for storage domain, it would fail.

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

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Create a cluster with gluster and virt capability enabled
2. Add the hypervisors ( which also has gluster installed ) to the cluster 
3. Create new volume
4. Observer create new volume dialog

Actual results:
---------------
'Optimize for Virt Store' is not checked by default

Expected results:
-----------------
'Optimize for Virt Store' should be checked by default.
Comment 1 Sahina Bose 2017-03-09 05:10:56 UTC 
Isn't this a dupe of Bug 1420687?
Comment 2 SATHEESARAN 2017-03-09 05:18:45 UTC 
(In reply to Sahina Bose from comment #1)
> Isn't this a dupe of Bug 1420687?

Yes, you are right. Thanks for pointing it out
Comment 3 SATHEESARAN 2017-03-09 05:20:03 UTC 

*** This bug has been marked as a duplicate of bug 1420687 ***