Bug 1568870

Summary: VDO feature should be enabled based on the availability of compatible gdeploy rpm
Product: [oVirt] cockpit-ovirt Reporter: SATHEESARAN <sasundar>
Component: GdeployAssignee: Gobinda Das <godas>
Severity: high Docs Contact:
Priority: unspecified    
Version: 0.11.12CC: bugs, sabose
Target Milestone: ---Flags: sasundar: ovirt-4.2?
sasundar: blocker?
sasundar: planning_ack?
sasundar: devel_ack?
sasundar: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-18 11:29:07 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:

Description SATHEESARAN 2018-04-18 10:55:22 UTC
Description of problem:
gdeploy supports VDO feature, only after the gdeploy builds > 2.0.2-19
So in case, if RHVH contains gdeploy < = 2.0.2-19, then VDO features should not be exposed in cockpit UI

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install gdeploy-2.0.2-19 ( which doesn't have support for VDO )
2. Use cockpit UI, to setup gluster configurations
3. Check for VDO feature exposure

Actual results:
VDO feature is exposed in cockpit UI even when gdeploy doesn't supports VDO

Expected results:
VDO feature should be exposed in the cockpit UI, only when gdeploy supports VDO

Comment 1 Sahina Bose 2018-04-18 11:29:07 UTC

*** This bug has been marked as a duplicate of bug 1568725 ***