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

Bug 1547705

Summary:	Incorrect logical size of the VDO volume in the generated gdeploy config file
Product:	[oVirt] cockpit-ovirt	Reporter:	SATHEESARAN <sasundar>
Component:	Gdeploy	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	0.11.7	CC:	bugs, lveyde, rhs-bugs, sabose
Target Milestone:	ovirt-4.2.2	Flags:	sasundar: ovirt-4.2? sasundar: planning_ack? rule-engine: devel_ack+ sasundar: testing_ack+
Target Release:	0.11.17
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.11.17-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1547704	Environment:
Last Closed:	2018-05-04 10:48:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1547704

Description SATHEESARAN 2018-02-21 19:00:26 UTC

+++ This bug was initially created as a clone of Bug #1547704 +++

Description of problem:
-----------------------
When user inputs the size of the bricks as 'X' GB, the logical size of the VDO volume as made available in the generated gdeploy config file is just 'X' which creates VDO volume with logical size 'X' MB

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

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Start RHHI installation from cockpit, by selecting 'Hosted Engine with Gluster'
2. While on the 'bricks' tab, provide the size of the brick
3. Enable dedupe and compression on all the bricks from the same device
4. Observe the generated gdeploy config file

Actual results:
---------------
generated gdeploy config file has the size in numeral without proper units, so VDO cli creates VDO volume takes it as MB by default

Expected results:
-----------------
The unit 'G' should be suffixed to the computed logical size


Additional info:
----------------
<actual_gdeploy_conf>
[vdo]
action=create
devices=sdb
names=vdovol_sdb
logicalsize=2000
</actual_gdeploy_conf>

<expected_gdeploy_conf>
[vdo]
action=create
devices=sdb
names=vdovol_sdb
logicalsize=2000G
</expected_gdeploy_conf>

Comment 1 SATHEESARAN 2018-04-30 09:35:03 UTC

Tested with cockpit-ovirt-dashboard-0.11.23

The logical size of the VDO volume has 'G' suffix

Comment 2 Sandro Bonazzola 2018-05-04 10:48:11 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.