Bug 1674608
| Summary: | Add check for 512b write suported on disks used for gluster bricks or not during gluster deployment | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Gobinda Das <godas> |
| Component: | gluster-ansible | Assignee: | Sachidananda Urs <surs> |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | rhhiv-1.6 | CC: | guillaume.pavese, rcyriac, rhs-bugs, sabose, sankarshan, sasundar |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.4.z Batch Update 4 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gluster-ansible-features-1.0.4-4.el7rhgs | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1674606 | Environment: | |
| Last Closed: | 2019-03-27 03:44:39 UTC | Type: | --- |
| 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: | 1674606, 1680597 | ||
|
Description
Gobinda Das
2019-02-11 16:42:54 UTC
github.com/gluster/gluster-ansible-features/pull/20/commits/5c375168 fixes the issue. This validation on the VDO disk failed and it blocks deployment
Validation is included for vdo devices and it errors out:
<snip>
failed: [dhcp37-124.lab.eng.blr.redhat.com] (item={u'vgname': u'gluster_vg_sdc', u'pvname': u'/dev/mapper/vdo_sdc'}) => {"changed": true, "cmd": ["cat", "/sys/block/vdo_sdc/queue/logical_block_size"], "delta": "0:00:01.006596", "end": "2019-02-23 12:57:13.896446", "failed_when_result": true, "item": {"pvname": "/dev/mapper/vdo_sdc", "vgname": "gluster_vg_sdc"}, "msg": "non-zero return code", "rc": 1, "start": "2019-02-23 12:57:12.889850", "stderr": "cat: /sys/block/vdo_sdc/queue/logical_block_size: No such file or directory", "stderr_lines": ["cat: /sys/block/vdo_sdc/queue/logical_block_size: No such file or directory"], "stdout": "", "stdout_lines": []}
failed: [dhcp37-138.lab.eng.blr.redhat.com] (item={u'vgname': u'gluster_vg_sdc', u'pvname': u'/dev/mapper/vdo_sdc'}) => {"changed": true, "cmd": ["cat", "/sys/block/vdo_sdc/queue/logical_block_size"], "delta": "0:00:01.009365", "end": "2019-02-23 12:57:14.234254", "failed_when_result": true, "item": {"pvname": "/dev/mapper/vdo_sdc", "vgname": "gluster_vg_sdc"}, "msg": "non-zero return code", "rc": 1, "start": "2019-02-23 12:57:13.224889", "stderr": "cat: /sys/block/vdo_sdc/queue/logical_block_size: No such file or directory", "stderr_lines": ["cat: /sys/block/vdo_sdc/queue/logical_block_size: No such file or directory"], "stdout": "", "stdout_lines": []}
</snip>
My mistake, I missed the mix of vdo and non-vdo disks scenario. Patch: https://github.com/gluster/gluster-ansible-features/pull/21/files fixes the issue. Tested with gluster-ansible-features-1.0.4-5 1. When the logical_size of the disk is not 512bytes, the validation fails 2. When the logical_size of the disk is 512bytes, then the validation succeeds, helping the complete deployment 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-2019:0661 |