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
*** Bug 1711959 has been marked as a duplicate of this bug. ***
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
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.
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