After conversing with Gobinda, this looks like a known design issue that either customer can create VDO enabled volumes or volumes without dedupe & compression.
This might not be useful for some scenarios. For instance, if the customer/user wants to create couple of volumes, one replica 3 volume with dedupe & compression enabled , and other arbitrated replicate volume, and doesn't want to enable to dedupe & compression on the arbiter bricks, this will not help.
This is a blocker in those cases.
@Sahina, what do you think ?
Also noticed that the mix of volumes with compression&dedupe enabled and disabled can't be created during RHHI deployment. This also seem to be a problem
Yes, we should be allowing a mix of deduped/non-deduped devices as long as the devices are different.
Gobinda, can this be addressed?
I am checking and will update.
Moving the bug as verified. Tested in version cockpit-ovirt-dashboard-0.11.28
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.
Since the problem described in this bug report should be
resolved in oVirt 4.2.4 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.