Bug 1712714

Summary:	Provide option for user to attach LVM Cache to specific thinpool
Product:	[oVirt] cockpit-ovirt	Reporter:	Gobinda Das <godas>
Component:	gluster-ansible	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.13.0	CC:	bugs, dparth
Target Milestone:	ovirt-4.3.6	Keywords:	ZStream
Target Release:	0.13.6	Flags:	sbonazzo: ovirt-4.3?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.13.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1721451 (view as bug list)		Environment:
Last Closed:	2019-09-26 19:42:53 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:
Bug Depends On:
Bug Blocks:	1721451

Description Gobinda Das 2019-05-22 06:40:00 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:

Comment 2 SATHEESARAN 2019-09-03 05:18:58 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 3 Sandro Bonazzola 2019-09-26 19:42:53 UTC

This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.