Bug 1721371

Summary:	Provide a way to cleanup gluster deployment from cockpit
Product:	[oVirt] cockpit-ovirt	Reporter:	Gobinda Das <godas>
Component:	gluster-ansible	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bipin <bshetty>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.13.0	CC:	bshetty, bugs, rhs-bugs, sabose, sasundar
Target Milestone:	ovirt-4.3.6	Keywords:	ZStream
Target Release:	0.13.6	Flags:	sbonazzo: ovirt-4.3?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.13.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1721370	Environment:
Last Closed:	2019-09-26 19:43:26 UTC	Type:	---
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:	1721370

Description Gobinda Das 2019-06-18 06:31:40 UTC

Description of problem:
 Now we don't have any option from cockpit UI to cleanup failed deployment.
If user wants to cleanup then manually cleanup playbook need to be executed.
So we should have option from UI to cleanup deployment.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 bipin 2019-08-28 04:57:43 UTC

Verified the bug with cockpit-ovirt-dashboard-0.13.6-1.el7ev.noarch.

Tested following :
================
1. Do a complete gluster deployment and then cleanup  
2. When the gluster deployment fails in between, do a cleanup.

Based on the above results closing the bug as verified.

Comment 2 Sandro Bonazzola 2019-09-26 19:43:26 UTC

This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

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