+++ This bug was initially created as a clone of Bug #1758148 +++
Description of problem:
----------------------------------------
When user enables dedupe and compression , the expanded disk size is 10 times the lv size and this field should be non-editable.
Version-Release number of selected component:
------------------------------------------------
rhvh-4.3.6.2-0.20190924
glusterfs-server-3.12.2-47.5.el7rhgs
cockpit-ovirt-dashboard-0.13.8-1.el7ev
How reproducible:
-------------------------------------------------
Every time
Steps to Reproduce:
-------------------------------------------------
1.Log in to cockpit and start gluster deployment.
2.In bricks tab under brick configuration check mark dedupe and compression checkbox
Actual results:
-------------------------------------------------
The expanded disk size field is editable.
Expected results:
--------------------------------------------------
The expanded disk size should be non editable .
--- Additional comment from RHEL Product and Program Management on 2019-10-03 12:16:17 UTC ---
This bug is automatically being proposed for RHHI-V 1.7 release at Red Hat Hyperconverged Infrastructure for Virtualization product, by setting the release flag 'rhiv‑1.7' to '?'.
If this bug should be proposed for a different release, please manually change the proposed release flag.
--- Additional comment from Mugdha Soni on 2019-10-03 12:17:09 UTC ---
(In reply to Sahina Bose from comment #2)
> Is there any issue if the size field is editable?
This was only against the expectation as the user should not be made to edit the size of the brick, as
that would be auto-computed.
Tested with cockpit-ovirt-dashboard-0.14.3 with the following steps:
1. Start HC deployment with 3 nodes
2. Reach the bricks tab and select 'Enable dedupe and compression' on the bricks
Observation is that the logical size field is not displayed. Its hidden as its the read-only field
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.
Since the problem described in this bug report should be
resolved in oVirt 4.4.0 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.