Bug 1674725
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: | gluster-ansible | Assignee: | Gobinda Das <godas> |
Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | rhhiv-1.6 | CC: | godas, khartsoe, lbailey, pmulay, rcyriac, rhs-bugs, sabose, sankarshan, sasundar, smohan, storage-qa-internal, surs |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS 3.4.z Batch Update 4 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
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’.
|
Story Points: | --- |
Clone Of: | 1674713 | Environment: | |
Last Closed: | 2019-03-27 03:44:39 UTC | Type: | --- |
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: | |||
Bug Blocks: | 1674713 |
Description
Gobinda Das
2019-02-11 16:56:07 UTC
Sac, Patch URL and devel_ack is missing on this bug Moving the needinfo to Gobinda. Gobinda please see Comment #2 Patch: https://github.com/gluster/gluster-ansible/pull/63 Provided devel_ack 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 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 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 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 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 |