Bug 1636425
| Summary: | Order of brick placement on the host is not preserved as defined in the playbook | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> | ||||
| Component: | gluster-ansible | Assignee: | Sachidananda Urs <surs> | ||||
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rhgs-3.4 | CC: | rcyriac, rhs-bugs, sabose, sankarshan, sasundar | ||||
| Target Milestone: | --- | Keywords: | ZStream | ||||
| Target Release: | RHGS 3.4.z Batch Update 1 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | gluster-ansible-roles-1.0.3 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1636427 (view as bug list) | Environment: | |||||
| Last Closed: | 2018-10-31 08:42:30 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: | 1636427 | ||||||
| Attachments: |
|
||||||
|
Description
SATHEESARAN
2018-10-05 11:09:05 UTC
Created attachment 1490851 [details]
Playbook used for gluster deployment
@sas this enhancement to playbook[1] by Gobinda should fix this ordering issue and the readability of the playbook as well. [1] https://github.com/gluster/gluster-ansible/commit/77dd66e Tested with ovirt-ansible-roles-1.0.3 The volumes are created on the hosts as per the playbook definitions 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-2018:3428 |