Bug 1573762

Summary: Multiple Slabsize value for VDO volumes not supported by Gdeploy
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Gobinda Das <godas>
Component: gdeployAssignee: Sachidananda Urs <surs>
Status: CLOSED ERRATA QA Contact: bipin <bshetty>
Severity: urgent Docs Contact:
Priority: high    
Version: rhgs-3.3CC: bugs, dkota, rcyriac, rhinduja, rhs-bugs, sabose, sankarshan, sasundar, smohan, storage-qa-internal, tnisan
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.3.1 Async   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gdeploy-2.0.2-27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-21 03:33:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1573138    
Bug Blocks: 1581561    

Description Gobinda Das 2018-05-02 08:26:56 UTC 
Description of problem:
Currently cockpit generates conf file with multiple slabsizes for multiple devices, but gdeploy does not support slabsizes with comma separated

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


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
Fails with multiple slabsizes

Expected results:
Should work for multiple slab sizes for multiple devices 

Additional info:
Comment 1 Sachidananda Urs 2018-05-03 06:11:45 UTC 
Commit: https://github.com/gluster/gdeploy/pull/509/commits/b4624b7ccfd30 fixes the issue.
Comment 5 SATHEESARAN 2018-06-06 10:52:21 UTC 
Verfied by the bug with the latest cockpit-dashboard-0.11.25. Now adding multiple slab size seems working.

Output:
[vdo1:10.70.45.29]
action=create
devices=sdb,sde
names=vdo_sdb,vdo_sde
logicalsize=164840G,3000G
blockmapcachesize=128M
readcache=enabled
readcachesize=20M
emulate512=on
writepolicy=auto
ignore_vdo_errors=no
slabsize=32G,32G
Comment 7 errata-xmlrpc 2018-06-21 03:33:15 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-2018:1958