Bug 1683345 - 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: rhhi
Version: rhhiv-1.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHHI-V 1.6
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1683355
Blocks: RHHI-V-1-6-Engineering-InFlight-BZs
TreeView+ depends on / blocked
 
Reported: 2019-02-26 16:03 UTC by Mugdha Soni
Modified: 2019-05-09 06:09 UTC (History)
4 users (show)

Fixed In Version: gluster-ansible-infra-1.0.3-3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1683355 (view as bug list)
Environment:
Last Closed: 2019-05-09 06:09:09 UTC
Embargoed:

Attachments (Terms of Use)
error in log files (6.29 KB, text/plain)
2019-02-26 16:05 UTC, Mugdha Soni 		no flags Details
thipool creation file (1.08 KB, text/plain)
2019-02-26 16:15 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
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1121 0 None None None 2019-05-09 06:09:18 UTC

Description Mugdha Soni 2019-02-26 16:03:51 UTC 
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.
------------------
Comment 1 Mugdha Soni 2019-02-26 16:05:04 UTC 
Created attachment 1538899 [details]
error in log files
Comment 2 Mugdha Soni 2019-02-26 16:15:20 UTC 
Created attachment 1538900 [details]
thipool creation file
Comment 3 Gobinda Das 2019-03-04 09:48:19 UTC 
Moving this to ON_QA as dependent bug is in ON_QA.
Comment 4 Mugdha Soni 2019-03-06 10:55:05 UTC 
Created attachment 1541326 [details]
RAID 5 disk type available
Comment 5 Mugdha Soni 2019-03-06 11:01:30 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 7 errata-xmlrpc 2019-05-09 06:09:09 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/RHEA-2019:1121
Note You need to log in before you can comment on or make changes to this bug.