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:
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>
As the dependent bug is ON_QA, moving this bug to ON_QA
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
Created attachment 1423107 [details] Cockpit_UI_Verified_Screenshot
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:3523