Bug 1887336 - RHHI-V deployment fails as local storage devices are excluded by filter
Summary: RHHI-V deployment fails as local storage devices are excluded by filter
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.8
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: RHHI-V 1.8.z Batch Update 2
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1883805
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-12 07:42 UTC by Gobinda Das
Modified: 2020-12-01 06:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1883805
Environment:
Last Closed: 2020-12-01 06:58:22 UTC
Embargoed:


Attachments (Terms of Use)

Description Gobinda Das 2020-10-12 07:42:31 UTC
Description of problem:
RHVH 4.4.2 has configured LVM filter to reject all the local storage devices, except for boot devices.
This leads to RHHI-V deployment fails to create LV on the intended disk as the disks are rejected by default.


The possible solution in this context is to:
1. Remove the existing LVM filter
# sed -i /^filter/d /etc/lvm/lvm.conf

2. Perform the required operation
               a. Gluster deployment as part of RHHI-V Deployment
               b. Volume creation / Volume expansion /Cluster Expansion

3. Regenerate LVM filter


Implementation should pay keen attention to following:

 - This will be integrated in to Deployment playbook. Role should remove the existing filter as the first operation and then post creating all bricks for the volumes,
playbook should regenerate the filter.

 - This should also apply for NBDE deployment playbook

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
LVm filter rejecting all devices, so the gluster deployment is failing

Expected results:
It should allow the devices to do deployment

Additional info:

--- Additional comment from Gobinda Das on 2020-09-30 09:48:12 UTC ---

Upstream PR: https://github.com/gluster/gluster-ansible-infra/pull/107

--- Additional comment from Prajith on 2020-10-01 07:14:09 UTC ---

The packages can be downloaded from the below links:-

Task Info: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=31670410
Build Info: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1337196

--- Additional comment from Yaniv Kaul on 2020-10-06 12:16:08 UTC ---

Can it be moved to ON_QA?

--- Additional comment from Prajith on 2020-10-06 13:19:36 UTC ---

(In reply to Yaniv Kaul from comment #3)
> Can it be moved to ON_QA?

Hi Yaniv,
I believe this is yet to be attached to errata, causing the bug not moved to ON_QA,


Hi Sahina,

I believe gobinda was working on attaching the build to errata I'm not sure, could you kindly attach this to errata as well?

--- Additional comment from errata-xmlrpc on 2020-10-06 14:11:43 UTC ---

Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHBA-2020:58392-01
https://errata.devel.redhat.com/advisory/58392

--- Additional comment from errata-xmlrpc on 2020-10-06 14:11:47 UTC ---

This bug has been added to advisory RHBA-2020:58392 by Sahina Bose (sabose)

Comment 3 SATHEESARAN 2020-11-04 14:11:51 UTC
Tested with gluster-ansible-infra-1.0.4-15.el8rhgs

Deployment is successful with this package. LVM filters are removed before Gluster deployment
and those are regenerated post gluster deployment


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