Bug 1655514

Summary: Shift from gdeploy to ansible roles
Product: [oVirt] cockpit-ovirt Reporter: Parth Dhanjal <dparth>
Component: GdeployAssignee: Parth Dhanjal <dparth>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: urgent    
Version: 0.11.29CC: bugs, cshao, godas, guillaume.pavese, sabose
Target Milestone: ovirt-4.3.1Flags: rule-engine: ovirt-4.3+
rule-engine: blocker+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.12.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1679091 (view as bug list) Environment:
Last Closed: 2019-03-01 10:20:21 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:
Bug Depends On:    
Bug Blocks: 1679091    

Description Parth Dhanjal 2018-12-03 10:59:48 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Sandro Bonazzola 2019-01-28 09:40:12 UTC
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.

Comment 2 SATHEESARAN 2019-02-25 17:36:29 UTC

Verified with cockpit-ovirt-dashboard-0.12.2 and it consumes gluster ansible roles

Tested with:
cockpit-ovirt-dashboard-0.12.2
gluster-ansible-cluster-1.0-1.el7rhgs.noarch
gluster-ansible-features-1.0.4-3.el7rhgs.noarch
gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch
gluster-ansible-infra-1.0.3-2.el7rhgs.noarch
gluster-ansible-roles-1.0.4-1.el7rhgs.noarch
gluster-ansible-repositories-1.0-1.el7rhgs.noarch

Comment 3 Sandro Bonazzola 2019-03-01 10:20:21 UTC
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

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