Bug 1819109 - [UPI on OSP] Destroy playbooks do not remove image-registry swift container and cinder volumes created from PVs
Summary: [UPI on OSP] Destroy playbooks do not remove image-registry swift container a...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.4.0
Assignee: Pierre Prinetti
QA Contact: David Sanz
Depends On: 1814651
TreeView+ depends on / blocked
Reported: 2020-03-31 08:46 UTC by Pierre Prinetti
Modified: 2020-06-11 10:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: The openstack UPI teardown scripts do not clear up Cinder volumes Consequence: Persistent volumes added to a UPI install are left untouched in the OpenStack cluster even after the teardown Ansible playbooks are successfully executed. Workaround (if any): Manually clear up any Cinder volume created in the cluster after teardown.
Clone Of: 1814651
Last Closed: 2020-05-13 22:01:42 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 3379 0 None closed [release-4.4] Bug 1819109: os UPI known issues: stale resources 2020-06-17 12:19:05 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-13 22:01:43 UTC

Description Pierre Prinetti 2020-03-31 08:46:42 UTC
+++ This bug was initially created as a clone of Bug #1814651 +++

Description of problem:

After creating a cluster using UPI scripts, we populate the internal registry and create cinder volumes from PVs

If destroy playbooks are executed, swift container is not deleted and also cinder volumes are still present on openstack

Version-Release number of the following components:

How reproducible:

Steps to Reproduce:
1.Install cluster using UPI on OSP
2.Populate internal registry and create PVs using the cinder storage class
3.Execute deletion playbooks

Actual results:
Following objects are still present in the cluster, after deletion is completed:
 - Cinder volumes from PVs
 - Swift container for image registry (bootstrap container is correctly deleted)

Expected results:
All cluster related objects are deleted

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

--- Additional comment from Pierre Prinetti on 2020-03-23 11:12:09 UTC ---

In a UPI installation, the user should look after the resources they created.

A user will only use UPI if their architecture is fatally different from our Reference architecture; and those differences will likely render our teardown playbooks useless (and exponentially more so as we fine-tune them on a specific use-case).

It would indeed be handy if the playbooks did all the work the installer is doing. However for the very nature of UPI, those changes will overcomplicate the playbooks without relieving much of the user's work; they'll have to adapt the scripts anyway.


--- Additional comment from David Sanz on 2020-03-25 13:16:08 UTC ---

I think that UPI installer should remove all elements that the IPI installer does.

If not, we should include a disclaimer in the docs about which objects have to be manually removed when UPI uninstaller playbooks ends

Comment 3 David Sanz 2020-04-02 11:34:07 UTC
Verified as change is only related to docs

Comment 5 errata-xmlrpc 2020-05-13 22:01:42 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.


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