+++ This bug was initially created as a clone of Bug #1610699 +++ Description of problem: ====================== Currently in Day 1, the thinp checkbox is made ready only and gets automatically unchecked while checking enable dedupe and compression. Same should be implemented in Day 2 ,which is currently read/write. Version-Release number of selected component (if applicable): =========================================================== cockpit-ovirt-dashboard-0.11.31-1.el7ev.noarch How reproducible: ================ 100% Steps to Reproduce: ================== 1.Login to cockpit -> Manage gluster -> Create volume 2.Navigate to the bricks tab Actual results: ============== Both thinp and enable dedupe & compression can be checked for a same device Expected results: ================ Should make thinp checkbox readonly Additional info: Attaching the screenshot for cockpit day 1 and day 2 --- Additional comment from bipin on 2018-08-01 04:53 EDT --- --- Additional comment from bipin on 2018-08-01 04:54 EDT ---
Created attachment 1472044 [details] Screenshot1
Created attachment 1472045 [details] Screenshot2
Created attachment 1521254 [details] Screenshot of bricks tab
Moving the bug to assigned state as when dedeupe and compression checkbox is checked the thinp checkbox for the first brick is not unchecked .This is possible in both the scenario when bricks are carved out of same disk or different disk.
Moving the target_milestone to 4.2.9
Resetting the target milestone to 4.3.0, there won't be any 4.2.9 after 4.3.0 GA
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Ovirt-4.3.1 already release, so moving to ovirt-4.3.2
Tested with cockpit-ovirt-dashboard-0.12.4 1. thinp checkbox is made read-only
This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.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.