Description of problem (please be detailed as possible and provide log
snippests):

The LVMCluster controller does not delete the lvm resources if there are any existing topolvm PVCs at the time of LVMCluster CR deletion.
However, the clean up does not happen as expected even after the PVCs are deleted.

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Is this issue reproducible?
Yes

Can this issue be reproduced from the UI?
N/A

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Install the LVM Operator and create an LVMCluster CR to configure it.
2. Create pods and PVCs using the topolvm provisioner storageclass
3. Delete the LVMCluster CR. The operator does not process the deletion because there are existing PVCs.
4. Delete the PVCs and pods.


Actual results:
The LVMCluster CR is not removed and the lvm resources are not deleted.

Expected results:
The LVMCluster CR is removed and the lvm resources are deleted.

Additional info: