When IBM Cloud Infrastructure bugs/outages prevent proper cleanup of resources, it can prevent the deletion of the Resource Group during cluster destroy. The errors returned because of this is not always helpful and can be confusing.

    4.16 (and earlier)

    80% when IBM Cloud Infrastructure experiences issues

    1. When there is a know issue with IBM Cloud Infrastructure (COS, Block Storage, etc.), create an IPI cluster on IBM Cloud
    2. Destroy the cluster
    

    WARNING Failed to delete resource group us-east-block-test-2-d5ssx: Resource groups with active or pending reclamation instances can't be deleted. Use the CLI commands "ibmcloud resource service-instances --type all" and "ibmcloud resource reclamations" to check for remaining instances, then delete the instances and try again.

    More descriptive details on the blocking resource service-instances (not always storage reclamation related). Potentially something helpful to provide to IBM Cloud Support for assistance.

    IBM Cloud is working on a PR to help enhance the debug details when these kind of errors occur.
At this time, an ongoing issue, https://issues.redhat.com/browse/OCPBUGS-28870, is causing these failures, where this additional debug information can help identify and guide IBM Cloud Support to resolve. But this information does not resolve that bug (which is an Infrastructure bug).