Bug 1721370

Summary: Provide a way to cleanup gluster deployment from cockpit
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Gobinda Das <godas>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: bipin <bshetty>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: lbailey, rhs-bugs, sasundar
Target Milestone: ---Keywords: ZStream
Target Release: RHHI-V 1.6.z Async Update   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Failed storage deployments can now be cleaned up from the Web Console.
Story Points: ---
Clone Of:
: 1721371 (view as bug list) Environment:
Last Closed: 2019-10-03 12:23:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1721371    
Bug Blocks:    

Description Gobinda Das 2019-06-18 06:30:25 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 4 bipin 2019-08-28 04:58:10 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 6 errata-xmlrpc 2019-10-03 12:23:57 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2963

Comment 7 Gobinda Das 2019-10-24 12:35:05 UTC
*** Bug 1619989 has been marked as a duplicate of this bug. ***