Bug 2076200

Summary:	Use 128MiB instead of 1GiB for he_metadata
Product:	[oVirt] ovirt-ansible-collection	Reporter:	Asaf Rachmani <arachman>
Component:	hosted-engine-setup	Assignee:	Asaf Rachmani <arachman>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0.0	CC:	bugs, michal.skrivanek, sbonazzo
Target Milestone:	ovirt-4.5.1	Keywords:	CodeChange, Triaged, ZStream
Target Release:	---	Flags:	sbonazzo: ovirt-4.5? sbonazzo: devel_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-ansible-collection-2.1.0	Doc Type:	Bug Fix
Doc Text:	Cause: Allocate 128MiB instead of 1GiB for he_metadata Consequence: Data is written at offset 4KiB*host_id, and since ovirt supports 250 hosts per dc, we don't really need to allocate 1GiB Fix: Allocate 128MiB instead of 1GiB for he_metadata Result: The he_metadata volume size is 128MiB	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-23 05:54:58 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:

Description Asaf Rachmani 2022-04-18 08:03:46 UTC

Allocate 128MiB instead of 1GiB for he_metadata
Each host in hosted-engine cluster is going to write to metadata volume
in his own reserved area (offset).
Data is written at offset 4KiB*host_id, and since ovirt supports 250 hosts per dc, we don't really need 1GiB.

Comment 1 Nikolai Sednev 2022-04-26 07:50:33 UTC

What's the reproduction steps?

Comment 2 Asaf Rachmani 2022-05-17 08:56:56 UTC

(In reply to Nikolai Sednev from comment #1)
> What's the reproduction steps?

1. Deploy HE 
2. Check HE metadata volume size

In addition, we need to see that there is no regression in automation tests.

Comment 3 Nikolai Sednev 2022-06-14 08:09:46 UTC

Can you please elaborate on the exact verification steps for this issue?
Thanks.

Comment 4 Asaf Rachmani 2022-06-20 13:58:58 UTC

(In reply to Nikolai Sednev from comment #3)
> Can you please elaborate on the exact verification steps for this issue?
> Thanks.

1. Deploy HE
2. Search for `he_metadata_disk_path` in the log files located in /var/log/var/log/ovirt-hosted-engine-setup/ directory
3. Get the relevant path
4. run ll -h path/to/file
5. verify the size is 128M

# cd /var/log/ovirt-hosted-engine-setup/
# grep -rnw ./ -e 'he_metadata_disk_path' | tail -1
./ovirt-hosted-engine-setup-ansible-create_target_vm-20220517082634-938mvo.log:5069:2022-05-17 08:29:15,200+0000 DEBUG var changed: host "localhost" var "he_metadata_disk_path" type "<class 'ansible.utils.unsafe_proxy.AnsibleUnsafeText'>" value: ""/rhev/data-center/mnt/192.168.155.1:_home_storage6/2f3816fd-0221-41de-8fdb-93df8bcb298f/images/5582d12d-563d-43c5-9a70-8fb2b151da6b/fc0e6701-a52a-4e04-afbd-e8c74bae3517""
# ll -h /rhev/data-center/mnt/192.168.155.1:_home_storage6/2f3816fd-0221-41de-8fdb-93df8bcb298f/images/5582d12d-563d-43c5-9a70-8fb2b151da6b/fc0e6701-a52a-4e04-afbd-e8c74bae3517
-rw-rw----. 1 vdsm kvm 128M Jun 20 13:56 /rhev/data-center/mnt/192.168.155.1:_home_storage6/2f3816fd-0221-41de-8fdb-93df8bcb298f/images/5582d12d-563d-43c5-9a70-8fb2b151da6b/fc0e6701-a52a-4e04-afbd-e8c74bae3517

Comment 5 Nikolai Sednev 2022-06-21 12:02:30 UTC

ovirt-ansible-collection-2.1.0-1.el8ev.noarch
ovirt-hosted-engine-setup-2.6.4-1.el8ev.noarch
ovirt-hosted-engine-ha-2.5.0-1.el8ev.noarch

Engine has:
ovirt-ansible-collection-2.1.0-1.el8ev.noarch
ovirt-engine-setup-4.5.1.2-0.11.el8ev.noarch


alma03 ~]# grep "he_metadata_disk_path" /var/log/ovirt-hosted-engine-setup/*
grep: /var/log/ovirt-hosted-engine-setup/engine-logs-2022-06-21T11:49:13Z: Is a directory
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-ansible-create_target_vm-20220621143801-c63hdl.log:2022-06-21 14:40:10,894+0300 DEBUG var changed: host "localhost" var "he_metadata_disk_path" type "<class 'ansible.utils.unsafe_proxy.AnsibleUnsafeText'>" value: ""/rhev/data-center/mnt/yellow-vdsb.qa.lab.tlv.redhat.com:_Compute__NFS_nsednev__he__1/3ed642f3-d912-42b3-8848-f07a8d8db4b5/images/16355a8f-1f7d-4828-8a77-2a0fbbd870da/795ba8ee-129c-49c1-816a-3183cf4d7929""

128M -rw-rw----. 1 vdsm kvm 128M Jun 21 15:00 /rhev/data-center/mnt/yellow-vdsb.qa.lab.tlv.redhat.com:_Compute__NFS_nsednev__he__1/3ed642f3-d912-42b3-8848-f07a8d8db4b5/images/16355a8f-1f7d-4828-8a77-2a0fbbd870da/795ba8ee-129c-49c1-816a-3183cf4d7929

Moving to verified.

Comment 6 Sandro Bonazzola 2022-06-23 05:54:58 UTC

This bugzilla is included in oVirt 4.5.1 release, published on June 22nd 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.1 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.