Bug 1552555 - [CNS][3.9] CNS uninstall playbook didn't remove glusterblock related resources
Summary: [CNS][3.9] CNS uninstall playbook didn't remove glusterblock related resources
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: 3.9.0
Assignee: Jose A. Rivera
QA Contact: Wenkai Shi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-07 10:33 UTC by Wenkai Shi
Modified: 2018-06-18 18:29 UTC (History)
6 users (show)

Fixed In Version: openshift-ansible-3.9.12-1.git.0.6155f6e.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-06-18 18:06:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Wenkai Shi 2018-03-07 10:33:30 UTC
Description of problem:
CNS uninstall playbook didn't remove glusterblock related resources

Version-Release number of the following components:
openshift-ansible-3.9.3-1.git.0.e166207.el7

How reproducible:
100%

Steps to Reproduce:
1. Deploy CNS on OCP
2. Execute cns uninstall playbook
# ansible-playbook -i hosts -vv /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/uninstall.yml
3.

Actual results:
# oc get all -n glusterfs
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-d67h5   1/1       Running   0          13m

NAME                                       DESIRED   CURRENT   READY     AGE
rc/glusterblock-storage-provisioner-dc-1   1         1         1         14m


Expected results:
All cns related resource should be removed.

Additional info:

Comment 1 Saravanakumar 2018-03-08 15:08:02 UTC
Corresponding changes to remove block(and s3) is available in upstream - but not yet merged in openshift-ansible-3.9.3-1.git.0.e166207.el7

Ref:
https://github.com/openshift/openshift-ansible/pull/7358

Comment 2 Jose A. Rivera 2018-03-08 15:15:01 UTC
Oh whoops, that'd be why.

Comment 3 Jose A. Rivera 2018-03-08 15:16:31 UTC
Cherrypick PR created: https://github.com/openshift/openshift-ansible/pull/7450

Comment 4 Jose A. Rivera 2018-03-12 12:43:25 UTC
PR merged

Comment 5 Wenkai Shi 2018-03-21 18:42:59 UTC
Verified with version openshift-ansible-3.9.12-1.git.0.6155f6e.el7, cns uninstall playbook can remove cns related resources. 

Before execute cns uninstall playbook:
# oc get po -n glusterfs
NAME                                          READY     STATUS    RESTARTS   AGE
glusterblock-storage-provisioner-dc-1-xd4q4   1/1       Running   0          19m
glusterfs-storage-78td9                       1/1       Running   0          26m
glusterfs-storage-v8ztb                       1/1       Running   0          26m
glusterfs-storage-vrl74                       1/1       Running   0          26m
heketi-storage-1-vw8vv                        1/1       Running   0          20m
# oc get sc 
NAME                 PROVISIONER               AGE
glusterfs-storage    kubernetes.io/glusterfs   21m
standard (default)   kubernetes.io/gce-pd      19m

After execute cns uninstall playbook:
# oc get po -n glusterfs
No resources found.
# oc get all -n glusterfs
No resources found.
# oc get sc 
NAME                 PROVISIONER            AGE
standard (default)   kubernetes.io/gce-pd   23m

Comment 6 Johnny Liu 2018-03-22 03:15:21 UTC
Per comment 5, move to verified.


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