Bug 1721371 - Provide a way to cleanup gluster deployment from cockpit
Summary: Provide a way to cleanup gluster deployment from cockpit
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: gluster-ansible
Version: 0.13.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.3.6
: 0.13.6
Assignee: Gobinda Das
QA Contact: bipin
URL:
Whiteboard:
Depends On:
Blocks: 1721370
TreeView+ depends on / blocked
 
Reported: 2019-06-18 06:31 UTC by Gobinda Das
Modified: 2019-09-26 19:43 UTC (History)
5 users (show)

Fixed In Version: cockpit-ovirt-0.13.6
Clone Of: 1721370
Environment:
Last Closed: 2019-09-26 19:43:26 UTC
oVirt Team: Gluster
Embargoed:
sbonazzo: ovirt-4.3?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 101571 0 master MERGED Option to cleanup deployment in failed deployment 2019-08-09 06:53:25 UTC
oVirt gerrit 102545 0 ovirt-4.3 MERGED Option to cleanup deployment in failed deployment 2019-08-12 07:01:52 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.