Bug 1721451

Summary: [RFE] Provide option for user to attach LVM Cache to specific thinpool
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: bugs, dparth, godas, guillaume.pavese, jcoscia, mkalinin, pasik, rhs-bugs
Target Milestone: ---Keywords: ZStream
Target Release: RHHI-V 1.6.z Async Update   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
LVM cache can now be attached to a specific thin pool, instead of only the first thin pool.
 Story Points: ---
Clone Of: 1712714 Environment:
Last Closed: 2019-10-03 12:23:57 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: 1712714    
Bug Blocks:    

Description SATHEESARAN 2019-06-18 10:26:46 UTC 
Description of problem:
-----------------------
 During deployment configuration in cockpit if user using 2 devices let's say sdb and sdc.The first one i.e. sdb is always thick lv but if user enabling lvm cache it's always using thinpool as sdb which is actually thik lv.So deployment is failing.

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


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Cockpit should use correct thin poll name for lvm cache and deployment should not fail.

Additional info:

--- Additional comment from SATHEESARAN on 2019-06-18 10:24:52 UTC ---

Targetting this feature to 4.3.6, as it needs lots of improvements on the UI design too
Comment 1 Sachidananda Urs 2019-06-20 04:11:24 UTC 
*** Bug 1711959 has been marked as a duplicate of this bug. ***
Comment 2 SATHEESARAN 2019-06-25 11:19:44 UTC 
As per the last QE & Dev sync-up, it was decided the change requires the change in UI component as well
and its dependent on the requirement of LVM cache for non-VDO use case
Comment 3 SATHEESARAN 2019-09-03 05:18:36 UTC 
verified with cockpit-ovirt-dashboard-0.13.6

LV cache section from the cockpit-wizard, now has clearly ask 
for the destination thinpool to be cached and it creates LV cache accordingly.
Comment 5 errata-xmlrpc 2019-10-03 12:23:57 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-2019:2963