Bug 1722231

Summary: [GSS] OCS/CNS uninstall fails to remove /var/lib/glusterd, /etc/glusterfs, and /var/lib/heketi from nodes
Product: OpenShift Container Platform Reporter: Anton Mark <amark>
Component: InstallerAssignee: Joseph Callen <jcallen>
Installer sub component: openshift-ansible QA Contact: Ashmitha Ambastha <asambast>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: asambast, gpei, jcallen, pprakash
Version: 3.11.0   
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-23 19:56:23 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:

Description Anton Mark 2019-06-19 18:17:01 UTC 
Description of problem:
[GSS] OCS/CNS uninstall fails to remove /var/lib/glusterd, /etc/glusterfs, and /var/lib/heketi from nodes


Version-Release number of the following components:



How reproducible:
Always.


Steps to Reproduce:
1. Install OCS with playbook (../openshift-ansible/playbooks/openshift-glusterfs/config.yml)
2. Uninstall OCS with playbook (../openshift-ansible/playbooks/openshift-glusterfs/uninstall.yml)
3. Check host nodes and above listed directories will still exist and have data in them.

Actual results:
Directories /var/lib/glusterd, /etc/glusterfs, and /var/lib/heketi still exist and have data in them.

Expected results:
Directories /var/lib/glusterd, /etc/glusterfs, and /var/lib/heketi should be deleted.

Additional info:
Upstream PR to resolve the issue I submitted. https://github.com/openshift/openshift-ansible/pull/11683
Comment 1 Joseph Callen 2019-06-20 13:05:33 UTC 
PR: https://github.com/openshift/openshift-ansible/pull/11683
openshift-ansible-3.11.119-1
Comment 7 errata-xmlrpc 2019-07-23 19:56:23 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:1753