Bug 1674713

Summary:	Provide a way to clean up deployment if deployment failed for some reason.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Gobinda Das <godas>
Component:	rhhi	Assignee:	Sahina Bose <sabose>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhhiv-1.6	CC:	guillaume.pavese, rhs-bugs, sankarshan, sasundar
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHHI-V 1.6
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gluster-ansible-roles-1.0.4-3.el7rhgs	Doc Type:	Enhancement
Doc Text:	If Red Hat Hyperconverged Infrastructure for Virtualization deployment fails, you can now start the deployment process from scratch by running the gluster_cleanup.yml playbook. See documentation for details.	Story Points:	---
Clone Of:
Clones:	1674725 (view as bug list)		Environment:
Last Closed:	2019-05-09 06:09:06 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:	1674725
Bug Blocks:	1672931

Description Gobinda Das 2019-02-11 16:55:00 UTC

Description of problem:
 Now there is no way to clean up failed deployment.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Gobinda Das 2019-02-18 14:11:19 UTC

Raised PR: https://github.com/gluster/gluster-ansible/pull/63

Comment 3 SATHEESARAN 2019-02-22 18:11:54 UTC

The dependent gluster-ansible bug is moved ON_QA, moving this bug too

Comment 4 SATHEESARAN 2019-03-06 08:10:24 UTC

Tested with gluster-ansible-roles-1.0.4-4
The cleanup playbook is available : /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_cleanup.yml

This script provides the cleanup of the environment

Comment 6 errata-xmlrpc 2019-05-09 06:09:06 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/RHEA-2019:1121