Bug 1848588 - Error while attaching the lvmcache to LUKS device thinpool
Summary: Error while attaching the lvmcache to LUKS device thinpool
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: gluster-ansible
Version: 0.14.8
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.4.1
: 0.14.9
Assignee: Parth Dhanjal
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1848467
TreeView+ depends on / blocked
 
Reported: 2020-06-18 14:58 UTC by SATHEESARAN
Modified: 2020-08-05 06:24 UTC (History)
4 users (show)

Fixed In Version: cockpit-ovirt-0.14.9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1848467
Environment:
Last Closed: 2020-08-05 06:24:34 UTC
oVirt Team: Gluster
Embargoed:
sasundar: ovirt-4.4?
sasundar: planning_ack?
sasundar: devel_ack?
sasundar: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 109841 0 master MERGED Attaching lvmcache to LUKS device thinpool 2020-09-25 12:44:00 UTC

Description SATHEESARAN 2020-06-18 14:58:55 UTC
Description of problem:
-----------------------
When NBDE setup is completed, the target device is created under /dev/mapper/luks_sdx. When attempting for RHHI-V deployment from web console(cockpit), and attaching the LVM cache, logic uses device name as '/dev/luks_sdc' instead of '/dev/mapper/luks_sdc'

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
cockpit-ovirt-dashboard-0.14.8


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


Steps to Reproduce:
-------------------
1. Start the HC deployment from cockpit
2. On the bricks tab provide the device name as '/dev/mapper/luks_sdc'
3. Enable LVM cache and provide SSD as '/dev/sdg'

Actual results:
---------------
Generated inventory file contains reference to '/dev/luks_sdc'

Expected results:
------------------
Generated inventory file should contain '/dev/mapper/luks_sdc'

--- Additional comment from SATHEESARAN on 2020-06-18 12:24:17 UTC ---

The generated inventory contains:

<snip>
      gluster_infra_cache_vars:
        - vgname: gluster_vg_luks_sdc
          cachedisk: '/dev/luks_sdc,/dev/sdg'
          cachelvname: cachelv_gluster_thinpool_gluster_vg_luks_sdc
          cachethinpoolname: gluster_thinpool_gluster_vg_luks_sdc
          cachelvsize: 220G
          cachemode: writethrough
</snip>

Expected is that the device should be */dev/mapper/luks_sdc*

<snip>
      gluster_infra_cache_vars:
        - vgname: gluster_vg_luks_sdc
          cachedisk: '/dev/mapper/luks_sdc,/dev/sdg'
          cachelvname: cachelv_gluster_thinpool_gluster_vg_luks_sdc
          cachethinpoolname: gluster_thinpool_gluster_vg_luks_sdc
          cachelvsize: 220G
          cachemode: writethrough
</snip>

--- Additional comment from SATHEESARAN on 2020-06-18 12:26:59 UTC ---

This error is also true for multipath configuration enabled, where the device name is '/dev/mapper/WWID'

for example: /dev/mapper/3600304801a48610125f9a6571e612c29

Comment 1 SATHEESARAN 2020-07-14 06:36:24 UTC
Tested with cockpit-ovirt-dashboard-0.14.9.el8rhgs

When attaching the LVM cache ( /dev/sdx ) with the LUKS device ( /dev/mapper/luks_sdx ),
the deployment happens in the right way.

Comment 2 Sandro Bonazzola 2020-08-05 06:24:34 UTC
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 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.


Note You need to log in before you can comment on or make changes to this bug.