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:
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
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)
All cluster related objects are deleted
Please attach logs from ansible-playbook with the -vvv flag
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.
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
Verified as fix is on the docs, not in the code
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.