Bug 1674713 - 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: rhhi
Version: rhhiv-1.6
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: RHHI-V 1.6
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1674725
Blocks: RHHI-V-1-6-Engineering-RFE-BZs
TreeView+ depends on / blocked
 
Reported: 2019-02-11 16:55 UTC by Gobinda Das
Modified: 2019-05-09 06:09 UTC (History)
4 users (show)

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.
Clone Of:
: 1674725 (view as bug list)
Environment:
Last Closed: 2019-05-09 06:09:06 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1121 0 None None None 2019-05-09 06:09:21 UTC

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