Chapter 5. Removing a RHOSO deployment from the RHOCP environment

Procedure

1. Delete all the OpenStackDataPlaneDeployment objects in the RHOSO namespace:

   $ oc delete OpenStackDataPlaneDeployment --all -n openstack

2. Delete all the OpenStackDataPlaneNodeSet objects in the RHOSO namespace:

   $ oc delete OpenStackDataPlaneNodeSet --all -n openstack

3. Delete all the OpenStackDataPlaneService objects in the RHOSO namespace:

   $ oc delete OpenStackDataPlaneService --all -n openstack

4. Delete the OpenStackControlPlane object from the RHOSO namespace:

   $ oc delete openstackcontrolplane \
    -l core.openstack.org/openstackcontrolplane -n openstack

5. Confirm that all the deployment pods are deleted:

   $ oc get pods -n openstack

6. Optional: Delete all Persistent Volume Claims (PVCs) from the RHOSO namespace:

   $ oc delete --all PersistentVolumeClaim -n openstack

   Tip

   Create a backup of your PVCs before deletion if you need to reuse them. For information about how to create a PVC backup, see the documentation for the storage backend used in your RHOSO environment.

7. Optional: Release the PV to make it available for other applications:

   $ oc patch PersistentVolume <pv_name> -p '{"spec":{"claimRef": null}}'

   Note

   If you intend to re-use the released PV, ensure that the PV is cleaned before use. For more information, see Lifecycle of a volume and claim in the RHOCP Storage guide.

8. Delete the Secret objects that contain the certificates issued for the control plane services and the data plane nodes when the RHOSO environment was deployed:

   $ oc delete secret -l service-cert -n openstack
   $ oc delete secret -l ca-cert -n openstack
   $ oc delete secret -l osdp-service -n openstack

   If the above commands return the message "No resources found" then the certificate secrets were automatically deleted when you deleted the control plane and data plane resources. For information about configuring the cert-manager Operator before RHOSO deployment to automatically delete the certificate secrets, see Deleting a TLS secret automatically upon Certificate removal in the RHOCP Security and Compliance guide.

9. Verify that the resources have been deleted from the namespace:

   $ oc get all
   No resources found.

10. Optional: Delete the namespace:

    $ oc delete namespace openstack

    Note

    You do not need to delete the namespace if you plan to create a new RHOSO deployment in the same namespace.

    If deleting the namespace is stuck in the terminating state:

    1. Check if any remaining objects have a finalizer:

       $ oc get $(oc api-resources|grep openstack.org|cut -d" " -f1 |paste -sd "," -),all -o custom-columns=Kind:.kind,Name:.metadata.name,Finalizers:.metadata.finalizers -n <namespace>

    2. Repeat the following command for each remaining object to remove the object finalizers and unblock deletion of each object:

       $ oc patch -n <namespace> <object-name> -p '{"metadata":{"finalizers":[]}}' --type=merge