Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1739147

Summary:	[RFE] Support 4k storage - ovirt-hosted-engine-ha
Product:	[oVirt] ovirt-hosted-engine-ha	Reporter:	Simone Tiraboschi <stirabos>
Component:	General	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.3.4	CC:	aefrat, bugs, nsoffer, tnisan
Target Milestone:	ovirt-4.3.8	Keywords:	ZStream
Target Release:	2.3.5	Flags:	sbonazzo: ovirt-4.3?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-hosted-engine-ha-2.3.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-26 16:32:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1592916

Description Simone Tiraboschi 2019-08-08 15:38:11 UTC

Description of problem:
ovirt-hosted-engine-ha assumes block size of 512 bytes initializing the lockspace volume.
Sanlock 3.7.3 supports also 4k locks; inq_lockspace, add_lockspace and rem_lockspace sanlock methods don't require any special handling.

Global and host blocks in the HE metadata volume were already 4k so no changes there.

Comment 1 Nikolai Sednev 2019-08-22 13:06:59 UTC

Need more info for reproduction steps.

Comment 4 Nir Soffer 2020-01-16 20:16:20 UTC

Removing old need info.

Comment 5 SATHEESARAN 2020-01-28 08:00:46 UTC

Tested with RHV 4.3.8 + RHGS 3.5.1 ( glusterfs-6.0-29.el7rhgs )

1. All the RHHI-V core cases are run with 4K disks as well as with 4K VDO devices.
2. Deployment and functionally works good without any issues

Comment 6 Sandro Bonazzola 2020-02-26 16:32:02 UTC

This bugzilla is included in oVirt 4.3.8 release, published on January 27th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.3.8 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Comment 7 Simone Tiraboschi 2020-05-28 09:40:55 UTC

Removing old need info.