Bug 1409861
| Summary: | cannot set volume options if the key has multiple values. | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | RamaKasturi <knarra> |
| Component: | gdeploy | Assignee: | Sachidananda Urs <surs> |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.2 | CC: | amukherj, rcyriac, rhinduja, rhs-bugs, smohan, storage-qa-internal |
| Target Milestone: | --- | ||
| Target Release: | RHGS 3.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gdeploy-2.0.1-9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-23 05:09:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1277939, 1351528 | ||
|
Description
RamaKasturi
2017-01-03 16:17:49 UTC
Patch: https://github.com/gluster/gdeploy/commit/38b80c0345 should fix the issue. If value has multiple items then they have to be separated by `;' or a `:' For example: [volume] action=create volname=ssl transport=tcp replica_count=2 force=yes brick_dirs=/data/1 key=auth.ssl-allow value="10.70.37.173;10.70.37.107" Or [volume] action=create volname=ssl transport=tcp replica_count=2 force=yes brick_dirs=/data/1 key=auth.ssl-allow value="10.70.37.173:10.70.37.107" proposing this as a blocker as the workaround suggested by sachi for enabling ssl on the volumes require multiple values to be set for a single key and this feature is not present in gdeploy as of now. Verified this bug on # rpm -qa | grep gdeploy gdeploy-2.0.1-9.el7rhgs.noarch Gdeploy is able to set multiple values in volume option Config file [hosts] 10.70.37.131 10.70.37.85 [volume1] action=create volname=disrt-replica1 transport=tcp replica=yes replica_count=2 force=yes brick_dirs=/mnt/data1/1,/mnt/data1/2,/mnt/data3/3 key=auth.ssl-allow value="10.70.37.192:10.70.37.142" [volume2] action=create volname=disrt-replica2 transport=tcp replica=yes replica_count=2 force=yes brick_dirs=/mnt/data2/2,/mnt/data2/3,/mnt/data3/4 key=auth.ssl-allow value="10.70.37.192:10.70.37.129" ================================ gluster v info Volume Name: disrt-replica1 Type: Distributed-Replicate Volume ID: 93a6e55a-5194-40a7-afe8-43cd67b1ae9f Status: Started Snapshot Count: 0 Number of Bricks: 3 x 2 = 6 Transport-type: tcp Bricks: Brick1: 10.70.37.131:/mnt/data1/1 Brick2: 10.70.37.85:/mnt/data1/1 Brick3: 10.70.37.131:/mnt/data1/2 Brick4: 10.70.37.85:/mnt/data1/2 Brick5: 10.70.37.131:/mnt/data3/3 Brick6: 10.70.37.85:/mnt/data3/3 Options Reconfigured: auth.ssl-allow: 10.70.37.192,10.70.37.142 performance.readdir-ahead: on Volume Name: disrt-replica2 Type: Distributed-Replicate Volume ID: d3f4dd59-3d16-4b00-8134-afdf5691e787 Status: Started Snapshot Count: 0 Number of Bricks: 3 x 2 = 6 Transport-type: tcp Bricks: Brick1: 10.70.37.131:/mnt/data2/2 Brick2: 10.70.37.85:/mnt/data2/2 Brick3: 10.70.37.131:/mnt/data2/3 Brick4: 10.70.37.85:/mnt/data2/3 Brick5: 10.70.37.131:/mnt/data3/4 Brick6: 10.70.37.85:/mnt/data3/4 Options Reconfigured: auth.ssl-allow: 10.70.37.192,10.70.37.129 performance.readdir-ahead: on 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://rhn.redhat.com/errata/RHEA-2017-0482.html |