Bug 1674725 - Provide a way to clean up deployment if deployment failed for some reason.
Summary: Provide a way to clean up deployment if deployment failed for some reason.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-ansible
Version: rhhiv-1.6
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
: RHGS 3.4.z Batch Update 4
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1674713
TreeView+ depends on / blocked
 
Reported: 2019-02-11 16:56 UTC by Gobinda Das
Modified: 2019-03-27 03:44 UTC (History)
12 users (show)

Fixed In Version: gluster-ansible-roles-1.0.4-3.el7rhgs
Doc Type: Enhancement
Doc Text:
With this update, a manual approach is introduced to cleanup gluster deployment in RHHI environment. This allows users to clean failed or existing gluster deployment by running the ‘hc_wizard_inventory.yml’ and ‘gluster_cleanup.yml’ playbook. Users can execute this command to clean gluster deployment: ‘ansible-playbook -i /etc/ansible/hc_wizard_inventory.yml /etc/ansible/role /gluster.ansible/playbooks/hc-ansible-deployment/task /gluster_cleanup.yml’.
Clone Of: 1674713
Environment:
Last Closed: 2019-03-27 03:44:39 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0661 0 None None None 2019-03-27 03:44:53 UTC

Description Gobinda Das 2019-02-11 16:56:07 UTC
+++ This bug was initially created as a clone of Bug #1674713 +++

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:

--- Additional comment from Red Hat Bugzilla Rules Engine on 2019-02-11 16:55:01 UTC ---

This bug is automatically being proposed for RHHI-V 1.6 release at Red Hat Hyperconverged Infrastructure for Virtualization product, by setting the release flag 'rhiv‑1.6' to '?'.

If this bug should be proposed for a different release, please manually change the proposed release flag.

Comment 2 SATHEESARAN 2019-02-19 19:43:02 UTC
Sac,

Patch URL and devel_ack is missing on this bug

Comment 3 Sachidananda Urs 2019-02-20 04:31:41 UTC
Moving the needinfo to Gobinda. Gobinda please see Comment #2

Comment 4 Gobinda Das 2019-02-20 05:16:45 UTC
Patch: https://github.com/gluster/gluster-ansible/pull/63
Provided devel_ack

Comment 5 Gobinda Das 2019-02-20 09:11:05 UTC
Hi laura,
 For this issue we need to provide documentation.Right now we don't support gluster deployment cleanup from UI.
We have cleanup playbook which needs to be executed manually if user wants to cleanup from first host where user doing deployment.

Command:
ansible-playbook -i /etc/ansible/hc_wizard_inventory.yml /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_cleanup.yml

Comment 9 Gobinda Das 2019-02-22 09:11:50 UTC
Hi Laura,
 The playbook path will be /usr/share/doc/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_cleanup.yml

So the command is: 

ansible-playbook -i /etc/ansible/hc_wizard_inventory.yml /usr/share/doc/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_cleanup.yml

Comment 12 Gobinda Das 2019-03-01 05:53:44 UTC
FYI..
As we decided to move gluster-ansible to /etc/ansible/roles/gluster.ansible from /usr/share/doc/gluster.ansible from next build, so the cleanup playbook location will be changed to /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_cleanup.yml

So for clean up the command will be:

ansible-playbook -i /etc/ansible/hc_wizard_inventory.yml /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/gluster_cleanup.yml

Comment 13 SATHEESARAN 2019-03-06 08:09:41 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 19 errata-xmlrpc 2019-03-27 03:44:39 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:0661


Note You need to log in before you can comment on or make changes to this bug.