Bug 1683355 - Gluster deployment fails for RAID 5.
Summary: Gluster deployment fails for RAID 5.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-ansible
Version: rhgs-3.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.4.z Batch Update 4
Assignee: Sachidananda Urs
QA Contact: Mugdha Soni
URL:
Whiteboard:
Depends On:
Blocks: 1683345
TreeView+ depends on / blocked
 
Reported: 2019-02-26 16:27 UTC by Mugdha Soni
Modified: 2019-04-03 10:06 UTC (History)
7 users (show)

Fixed In Version: gluster-ansible-infra-1.0.3-3
Doc Type: Bug Fix
Doc Text:
Previously, deployment was aborted with the "Unknown disktype" message as a system check for RAID5 was missing. This update adds the disk type RAID5 along with the required calculations to set values for LVM. Thus, deployments for RAID5 are successful.
Clone Of: 1683345
Environment:
Last Closed: 2019-03-27 03:44:39 UTC
Embargoed:


Attachments (Terms of Use)
error in log files (6.29 KB, text/plain)
2019-02-26 16:28 UTC, Mugdha Soni
no flags Details
thinpool creation file (1.08 KB, text/plain)
2019-02-26 16:28 UTC, Mugdha Soni
no flags Details
RAID 5 disk type available (90.83 KB, image/png)
2019-03-06 10:55 UTC, Mugdha Soni
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0661 0 None None None 2019-03-27 03:44:53 UTC

Description Mugdha Soni 2019-02-26 16:27:14 UTC
+++ This bug was initially created as a clone of Bug #1683345 +++

Description of problem:
---------------------------
In gluster deployment when the RAID type is set as RAID 5 the deployment fails stating error "Unknown disktype. Allowed disktypes: JBOD, RAID6, RAID10".
Whereas RAID 5 disktype is also allowed 


Version-Release number of selected component :
-----------------------------------------------
rhvh-4.3.0.5-0.20190225
glusterfs-server-3.12.2-45
cockpit-ovirt-dashboard-0.12.3-1.el7ev
gluster-ansible-cluster-1.0-1.el7rhgs.noarch
gluster-ansible-features-1.0.4-3.el7rhgs.noarch
gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch
gluster-ansible-infra-1.0.3-2.el7rhgs.noarch
gluster-ansible-roles-1.0.4-3.el7rhgs.noarch
gluster-ansible-repositories-1.0-1.el7rhgs.noarch

How reproducible:
------------------
Everytime

Steps to Reproduce:
--------------------
1.Log in to cockpit UI and fill in all the required parameters
2.In brick tab choose RAID 5 as disk type.

Actual results:
-------------------
Deployment fails for RAID 5 disktype.

Expected results:
-------------------
Deployment should not fail for RAID 5.

Additional info:
-----------------
Under location /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks in file thin_pool_create.yml doesnot hold RAID5 as disk type.
------------------

--- Additional comment from Mugdha Soni on 2019-02-26 16:05 UTC ---



--- Additional comment from Mugdha Soni on 2019-02-26 16:15 UTC ---

Comment 2 Mugdha Soni 2019-02-26 16:28:11 UTC
Created attachment 1538901 [details]
error in log files

Comment 3 Mugdha Soni 2019-02-26 16:28:47 UTC
Created attachment 1538902 [details]
thinpool creation file

Comment 4 SATHEESARAN 2019-02-27 09:56:10 UTC
This bug is the release blocker for RHHI-V 1.6 as the RAID-5 can't be supported without the fix

Comment 7 Sachidananda Urs 2019-02-28 11:57:57 UTC
PR: https://github.com/gluster/gluster-ansible-infra/pull/54

Comment 9 Mugdha Soni 2019-03-06 10:55:36 UTC
Created attachment 1541327 [details]
RAID 5 disk type available

Comment 10 Mugdha Soni 2019-03-06 11:01:38 UTC
Tested with the following:-
rhvh-4.3.0.5-0.20190305
gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch
gluster-ansible-roles-1.0.4-4.el7rhgs.noarch
gluster-ansible-infra-1.0.3-3.el7rhgs.noarch
gluster-ansible-repositories-1.0-1.el7rhgs.noarch
gluster-ansible-features-1.0.4-5.el7rhgs.noarch
gluster-ansible-cluster-1.0-1.el7rhgs.noarch

While gluster deployment RAID 5 disk type was available in drop down and deployment was successful when disktype RAID 5 is chosen.
Hence , moving the bug to verified.

Comment 14 errata-xmlrpc 2019-03-27 03:44:39 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, 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:0661


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