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

Bug 1547513

Summary:

[Cockpit ] Logical size of the devices should be computed for all values gives in physical device

Product:

[oVirt] cockpit-ovirt

Reporter:

bipin <bshetty>

Component:

Gdeploy

Assignee:

Gobinda Das <godas>

Status:

CLOSED CURRENTRELEASE

QA Contact:

bipin <bshetty>

Severity:

high

Docs Contact:

Priority:

unspecified

Version:

0.11.7

CC:

bugs, lveyde, rhs-bugs, sabose, sasundar

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:

Unspecified

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:

1547509

Environment:

Last Closed:

2018-04-18 12:25:56 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:

1547509

Attachments:

Description	Flags
Cockpit_UI_Verified_Screenshot	none

Description bipin 2018-02-21 13:15:41 UTC

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

Description of problem:

In the cockpit UI, during the Gluster storage deployment while checking the enable Dedupe and Compression option the logical size isn't automatically generated. Currently the logical size is increased 4 times the physical volumes only for the default values.


Version-Release number of selected component (if applicable):
cockpit-ovirt-dashboard-0.11.11-0.1.el7ev.noarch
kmod-kvdo-6.1.0.146-13.el7.x86_64
vdo-6.1.0.146-16.x86_64
gdeploy-2.0.2-22.el7rhgs.noarch

How reproducible:
Everytime

Steps to Reproduce:
1. Login to the cockpit dashboard
2. Hosted engine deployment with gluster
3. In the bricks tab check the Enable Dedupe & Compression and look for the Logical size

Actual results:
The logical size is generated only for the default value set

Expected results:
The logical size should be generated automatically for any physical size given

Additional info:

--- Additional comment from Red Hat Bugzilla Rules Engine on 2018-02-21 08:11:30 EST ---

This bug is automatically being proposed for the current release of Red Hat Hyperconverged Infrastructure (RHHI) under active development, by setting the release flag 'rhhi‑2.0' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

Comment 1 SATHEESARAN 2018-03-06 07:09:36 UTC

The logical size of the VDO volume should 10x as per the response from Dennis Keefe, currently the model chosen provides 4x

Here is the snippet from Dennis Keefe's response
<snip_from_mail>
> 2. vdoLogicalSize = 10 x ( Disk physical size )
> In actual, the cockpit implementation does 4 x size of physical disk.
> I read from the RHEL 7.5 storage admin guide, about the recommendation of 10:1

 The cockpit implementation will allow much large size, though you have to manually change the settings.
10x is typical for VMs.  I agree with this setting.

</snip_from_mail>

Comment 2 SATHEESARAN 2018-04-17 11:09:24 UTC

Moved to VERIFIED state by mistake.

Comment 3 bipin 2018-04-17 15:36:44 UTC

Verified the bug in the below component version's successfully.

Component versions's:
gdeploy-2.0.2-23.el7rhgs.noarch
cockpit-ovirt-dashboard-0.11.20-1.el7ev.noarch

Steps:
1. Install VDO 
2. Start the gluster deployment via cockpit UI and check the compression and deduplication tab.
3. Could see the logical size 10 times the physical size.

Result:
Please find the attached screeshot of the verification

Comment 4 bipin 2018-04-17 15:37:25 UTC

Created attachment 1423108 [details]
Cockpit_UI_Verified_Screenshot

Comment 5 Sandro Bonazzola 2018-04-18 12:25:56 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.