Bug 1815542 - RHHI-V gluster deployment fails at thinpool creation with size greater than few TBs
Summary: RHHI-V gluster deployment fails at thinpool creation with size greater than f...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHHI-V 1.8
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1815546
Blocks: RHHI-V-1.8-Engineering-Inflight-BZs
TreeView+ depends on / blocked
 
Reported: 2020-03-20 14:25 UTC by SATHEESARAN
Modified: 2020-08-04 14:52 UTC (History)
1 user (show)

Fixed In Version: gluster-ansible-infra-1.0.4-7.el8rhgs
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1815546 (view as bug list)
Environment:
rhhiv, rhel8
Last Closed: 2020-08-04 14:52:05 UTC
Embargoed:


Attachments (Terms of Use)
deployment-log (44.86 KB, application/octet-stream)
2020-03-20 15:14 UTC, SATHEESARAN
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:3314 0 None None None 2020-08-04 14:52:21 UTC

Description SATHEESARAN 2020-03-20 14:25:59 UTC
Description of problem:
------------------------
RHHI-V gluster deployment fails with thinpool creation, when the thinpool size exceeds few TBs. In this case, the size of thinpool is 120TB

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gluster-ansible-repositories-1.0.1-2.el8rhgs.noarch
gluster-ansible-features-1.0.5-6.el8rhgs.noarch
gluster-ansible-infra-1.0.4-6.el8rhgs.noarch
gluster-ansible-maintenance-1.0.1-2.el8rhgs.noarch
gluster-ansible-cluster-1.0-1.el8rhgs.noarch
gluster-ansible-roles-1.0.5-7.el8rhgs.noarch

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

Steps to Reproduce:
--------------------
1. Start the RHHI-V deployment, with brick size of 120TB

Actual results:
---------------
Deployment fails while creating the thinpool with smaller chunksize

Expected results:
-----------------
Deployment should succeed

Comment 2 SATHEESARAN 2020-03-20 14:44:03 UTC
As per my conjecture, this looks like problem because of incorrect inclusion of content from master branch.

On RHEL 7 based RHHI-V 1.7 the content looks like:
[root@ ]# ls -l /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks
total 36
-rw-r--r--. 1 root root 2264 Jan 24 16:39 cache_setup.yml
-rw-r--r--. 1 root root 1331 Jan 24 16:39 fscreate.yml
-rw-r--r--. 1 root root 3637 Jan 24 16:39 main.yml
-rw-r--r--. 1 root root 2222 Jan 24 16:39 mount.yml
-rw-r--r--. 1 root root  230 Jan 24 16:39 thick_lv_create.yml
-rw-r--r--. 1 root root 1150 Jan 24 16:39 thin_pool_create.yml
-rw-r--r--. 1 root root  383 Jan 24 16:39 thin_volume_create.yml
-rw-r--r--. 1 root root 1315 Jan 24 16:39 vdo_create.yml
-rw-r--r--. 1 root root 2002 Jan 24 16:39 vg_create.yml


The same content with the latest RHEL-8 looks like:
[root@ ]# ls -l /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks
total 92
-rw-r--r--. 1 root root  1427 Mar 13 09:54 bind_tang_server.yml
-rw-r--r--. 1 root root   962 Mar 13 09:54 blacklist_mpath_devices.yml
-rw-r--r--. 1 root root  6177 Mar 13 09:54 cache_setup.yml
-rw-r--r--. 1 root root  4112 Mar 13 09:54 fscreate.yml
-rw-r--r--. 1 root root   595 Mar 13 09:54 fstrim_service.yml
-rw-r--r--. 1 root root  2326 Mar 13 09:54 get_vg_groupings.yml
-rw-r--r--. 1 root root  2637 Mar 13 09:54 luks_device_encrypt.yml
-rw-r--r--. 1 root root   743 Mar 13 09:54 lvm_config.yml
-rw-r--r--. 1 root root  1711 Mar 13 09:54 lvm_kernelparams.yml
-rw-r--r--. 1 root root   868 Mar 13 09:54 main-lvm.yml
-rw-r--r--. 1 root root  4074 Mar 13 09:54 main.yml
-rw-r--r--. 1 root root  2497 Mar 13 09:54 mount.yml
-rw-r--r--. 1 root root  4815 Mar 13 09:54 thick_lv_create.yml
-rw-r--r--. 1 root root 11748 Mar 13 09:54 thin_pool_create.yml
-rw-r--r--. 1 root root  6652 Mar 13 09:54 thin_volume_create.yml
-rw-r--r--. 1 root root  3327 Mar 13 09:54 vdo_create.yml
-rw-r--r--. 1 root root  2951 Mar 13 09:54 vg_create.yml

Also the content of thin_pool_create.yml is totally different with the latest.

Comment 3 SATHEESARAN 2020-03-20 15:14:30 UTC
Created attachment 1671941 [details]
deployment-log

Comment 5 SATHEESARAN 2020-03-30 14:48:02 UTC
Dependent bug is ON_QA, and moving this bug also ON_QA

Comment 6 SATHEESARAN 2020-03-30 14:48:26 UTC
Tested with gluster-ansible-infra-1.0.4-7 and RHVH 4.4. based on el8.2

thinpool creation step in gluster deployment process of RHHI-V deployment is successful

Comment 8 errata-xmlrpc 2020-08-04 14:52:05 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 (RHHI for Virtualization 1.8 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/RHEA-2020:3314


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