Bug 1568725

Summary:	Enable VDO option Only if gdeploy version is greater than or equals to gdeploy-2.0.2-25
Product:	[oVirt] cockpit-ovirt	Reporter:	Gobinda Das <godas>
Component:	Gdeploy	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	0.11.7	CC:	bugs, rbarry, sabose, sasundar, surs
Target Milestone:	ovirt-4.2.3	Flags:	rule-engine: ovirt-4.2? rule-engine: blocker+ sasundar: planning_ack? rule-engine: devel_ack+ sasundar: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.11.23-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-10 06:33:08 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:
Embargoed:

Description Gobinda Das 2018-04-18 07:47:39 UTC

Description of problem:
 Currently gdeploy supports full feature of VDO from gdeploy-2.0.2-25 on wards.
Cockpit should make sure the version is greater or equal to enable vdo option.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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

*** Bug 1568870 has been marked as a duplicate of this bug. ***

Comment 2 Ryan Barry 2018-04-18 12:02:14 UTC

This will need to be 4.2.4 unless it is a blocker or exception.

Comment 4 SATHEESARAN 2018-04-28 08:53:34 UTC

Tested with cockpit-ovirt-dashboard-0.11.23

1. Installed gdeploy-2.0.2-19, and verified that the VDO options are not enabled in UI
2. Installed gdeploy-2.0.2-26 and verified that the VDO options are enabled

Comment 5 Sandro Bonazzola 2018-05-10 06:33:08 UTC

This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 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.