Bug 1674606

Summary:	Add check for 512b write supported on disks used for gluster bricks or not during gluster deployment
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Gobinda Das <godas>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED ERRATA	QA Contact:	bipin <bshetty>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhhiv-1.6	CC:	guillaume.pavese, rhs-bugs, sankarshan, sasundar, surs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHHI-V 1.6
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gluster-ansible-features-1.0.4-3.el7rhgs	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1674608 1680597 (view as bug list)		Environment:
Last Closed:	2019-05-09 06:09:06 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:	1674608
Bug Blocks:	1672931, 1680597

Description Gobinda Das 2019-02-11 16:42:16 UTC

Description of problem:
 Right now there is no validation for 512b write suported on disks used for gluster bricks or not during gluster deployment

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 SATHEESARAN 2019-02-22 18:14:47 UTC

The dependent gluster-ansible bug is ON_QA, moving this bug too

Comment 3 SATHEESARAN 2019-02-23 11:42:00 UTC

The dependent bug failed verification


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>

Comment 4 Gobinda Das 2019-03-05 11:39:22 UTC

Moving thi to ON_QA as dependent bug is in ON_QA

Comment 5 SATHEESARAN 2019-03-07 11:25:42 UTC

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

Comment 7 errata-xmlrpc 2019-05-09 06:09:06 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-2019:1121