1553032 – ansible playbook to uninstall glusterfs doesn't remove gluster-block provisioner pod

Bug 1553032 - ansible playbook to uninstall glusterfs doesn't remove gluster-block provisioner pod

Summary: ansible playbook to uninstall glusterfs doesn't remove gluster-block provisio...

Keywords:
Status:	CLOSED CURRENTRELEASE
Alias:	None
Product:	Red Hat Gluster Storage
Classification:	Red Hat Storage
Component:	CNS-deployment
Sub Component:
Version:	cns-3.9
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	high
Target Milestone:	---
Target Release:	CNS 3.9
Assignee:	Saravanakumar
QA Contact:	krishnaram Karthick
Docs Contact:
URL:
Whiteboard:
Depends On:	1553034
Blocks:	1526415
TreeView+	depends on / blocked

Reported:	2018-03-08 05:12 UTC by krishnaram Karthick
Modified:	2018-04-17 15:30 UTC (History)
CC List:	10 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Clones:	1553034 (view as bug list)
Environment:
Last Closed:	2018-04-17 15:30:51 UTC
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Description krishnaram Karthick 2018-03-08 05:12:13 UTC

Description of problem:

'ansible-playbook  /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/uninstall.yml' doesn't remove glusterblock provisioner pods. This successfully removes glusterfs & heketi related services.

output after running uninstall:

# oc get all
NAME                                                    REVISION   DESIRED   CURRENT   TRIGGERED BY
deploymentconfigs/glusterblock-storage-provisioner-dc   1          1         1         config

NAME                                             READY     STATUS    RESTARTS   AGE
po/glusterblock-storage-provisioner-dc-1-qbjfl   1/1       Running   0          23h

NAME                                       DESIRED   CURRENT   READY     AGE
rc/glusterblock-storage-provisioner-dc-1   1         1         1         23h

NAME                               TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
svc/glusterfs-dynamic-claim-file   ClusterIP   172.31.40.166   <none>        1/TCP     21h


Version-Release number of selected component (if applicable):
openshift-ansible-roles-3.9.2-1.git.0.1a855b3.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. Uninstall glusterfs using /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/uninstall.yml playbook
2. check if all resources related to glusterfs are deleted

Comment 5 Saravanakumar 2018-03-14 08:10:54 UTC

This is targeted for OCP-3.9.z - Refer Bug #1553034

Comment 7 Humble Chirammal 2018-03-22 10:31:45 UTC

As per update from Jose, this is available in OCP 3.9 ansible builds. I am moving this to "ON_QA"

Comment 8 krishnaram Karthick 2018-03-29 12:03:32 UTC

This issue is fixed in 3.9.14 version of OCP. Moving the bug to verified.


[root@dhcp46-101 ~]# oc project glusterfs
Already on project "glusterfs" on server "https://dhcp46-101.lab.eng.blr.redhat.com:8443".
[root@dhcp46-101 ~]# oc get all
No resources found.

[root@dhcp46-101 ~]# oc version
oc v3.9.14
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://dhcp46-101.lab.eng.blr.redhat.com:8443
openshift v3.9.14
kubernetes v1.9.1+a0ce1bc657

[root@dhcp46-101 ~]# rpm -qa| grep 'openshift-ansible'
openshift-ansible-roles-3.9.14-1.git.0.ca2cfc3.el7.noarch
openshift-ansible-playbooks-3.9.14-1.git.0.ca2cfc3.el7.noarch
openshift-ansible-docs-3.9.14-1.git.0.ca2cfc3.el7.noarch
openshift-ansible-3.9.14-1.git.0.ca2cfc3.el7.noarch

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