Bug 1017515

Summary: Virt-optimized volume still gives option to optimize for virt.
Product: Red Hat Enterprise Virtualization Manager Reporter: Tim Hildred <thildred>
Component: ovirt-engine-webadmin-portalAssignee: Sahina Bose <sabose>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 3.3.0CC: acathrow, ecohen, iheim, Rhev-m-bugs, sabose, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: gluster
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-19 09:28:34 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 Tim Hildred 2013-10-10 05:24:41 UTC
Description of problem:

I created a new volume from the Engine, and selected "optimize for virt.store"

Volume is created, I hit start. Volume starts.

Button "Optimize for virtstore" still shows on volume that was already optimized. 

Expected behaviour:
Engine should be able to tell if a volume has already been optimized, and adjust which buttons to show the user. 

Like, when I click "Start", I can't click "Start" again.

Comment 1 Sahina Bose 2013-10-31 07:16:44 UTC
Currently, there's no foolproof way to know if a volume has already been optimized. If the user has set the volume option from UI, then we can identify it.

But if options are set manually from UI, engine does not know of it and cannot mark it.

Comment 2 Sahina Bose 2013-12-19 09:28:34 UTC

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