Persistent Volume Claims remains bound to z/OS Cloud Broker instance after instance has been deleted

[mayur-raja]

Bug Report

What did you do?

I created zoscloudbroker which failed because I had failed to set a storage class. While this broker instance was in a failed state, I created zoscloudbroker2 and set the storage class. This was successful.

I then deleted both broker instances. The deletions were both successful.

I then recreated zoscloudbroker and set the storage class. This was successful.

I then selected Storage and Persistent Volume Claims and noticed that there was a bound PVC for zoscloudbroker2.

What did you expect to see?

Given that the zoscloudbroker2 had been successfully deleted, I would not have expected to see a PVC for it.

What did you see instead? Under which circumstances?

I saw instances of resources associated with a deleted broker instance. This should not occur as it requires end users to perform manual cleanup and hence adds to their admin overhead.

Collection Version

$ ansible-galaxy collection verify ibm.operator_collection_sdk

Note: The above command failed on my system so I got the version from the OpenShift panel:

IBM® z/OS® Cloud Broker
2.2.0 provided by IBM

Possible Solution

All resources associated with zoscloudbroker2 should ideally be deleted when the broker is deleted. If it is a requirement to first delete the PVC, then deletion of the broker should have failed with an indication that the PVC must first be deleted.

Additional context

For now, I manually deleted the PVC for zoscloudbroker2.

[mayur-raja]

Closing this here as I had raised this against the wrong category. Now raised as https://github.ibm.com/IBM-Z-and-Cloud-Modernization-Stack/zoscb/issues/2285 .