Bug 1654716 - [openstack] Uninstall playbook doesn't remove the pvcs created in the environment
Summary: [openstack] Uninstall playbook doesn't remove the pvcs created in the environ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Johnny Liu
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-29 13:51 UTC by Eduardo Minguez
Modified: 2018-11-29 15:29 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-29 15:29:43 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Eduardo Minguez 2018-11-29 13:51:44 UTC
Description of problem:

OCP deployed on OSP using the https://github.com/openshift/openshift-ansible/blob/master/playbooks/openstack/ playbooks. During the cluster lifetime, some users created pvcs, hence cinder volumes (kubernetes-pvc-XXX)

When using the openstack uninstall playbook (https://github.com/openshift/openshift-ansible/blob/master/playbooks/openstack/openshift-cluster/uninstall.yml) those cinder volumes are not deleted.

Version-Release number of the following components:
OCP 3.11.43

How reproducible:
Install a cluster with openstack-openshift playbooks, create some sample apps with persistent storage, then uninstall the cluster.

Steps to Reproduce:

Actual results:
Cinder volumes corresponding to pvcs are not deleted.

Expected results:
Having a flag/variable such as 'keep_pvcs=true/false' and then in the uninstall process run something as:
'for n in $(oc get namespaces -o name | cut -d'/' -f2); do oc delete --all pvc -n ${n}; done' (but ansibilized here https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_openstack/tasks/unprovision.yml)

Additional info:

Comment 1 Scott Dodson 2018-11-29 15:29:43 UTC
The installer only manages items it directly creates. We cannot go down the rabbit hole of cleaning up all resources that may have been created by the cluster at this time.

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