Bug 1883805 - 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 ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-ansible
Version: rhhiv-1.8
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: RHGS 3.5.z Async Update
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1887336
TreeView+ depends on / blocked
 
Reported: 2020-09-30 09:41 UTC by Gobinda Das
Modified: 2020-11-24 12:38 UTC (History)
7 users (show)

Fixed In Version: gluster-ansible-infra-1.0.4-14
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1887336 (view as bug list)
Environment:
Last Closed: 2020-11-24 12:37:41 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:5220 0 None None None 2020-11-24 12:38:06 UTC

Description Gobinda Das 2020-09-30 09:41:36 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:

Comment 1 Gobinda Das 2020-09-30 09:48:12 UTC
Upstream PR: https://github.com/gluster/gluster-ansible-infra/pull/107

Comment 3 Yaniv Kaul 2020-10-06 12:16:08 UTC
Can it be moved to ON_QA?

Comment 4 Prajith 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?

Comment 10 SATHEESARAN 2020-11-04 14:11:09 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

Comment 14 errata-xmlrpc 2020-11-24 12:37:41 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 (gluster-ansible bug fix and enhancement update), 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-2020:5220


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