Can't delete cloud credential if there is an RKE2/k3s cluster rely on it
Import Harvester cluster to Rancher v2.6-head.
Create a cloud credential for Harvester.
Create RKE2/k3s clusters on Harvester.
Try to remove Harvester's cloud credential. It can't be removed.
Remove RKE2/k3s clusters.
Remove Harvester's cloud credential. It can be removed now.
Remove harvester cluster if there is an RKE2/k3s cluster rely on it
Import Harvester cluster to Rancher v2.6-head.
Create a cloud credential for Harvester.
Create RKE2/k3s clusters on Harvester.
Remove the Harvester cluster in Virtualization Management page. Harvester cluster can be removed.
Remove RKE2/k3s clusters in Rancher. RKE2/k3s clusters can be removed, but related VMs are still running in Harvester because Rancher can't connect to the Harvester cluster.
Remove related VMs in Harvester. They can be removed.
Remove Harvester's cloud credential. It can be removed.
What's the test to develop? Please describe
Can't delete cloud credential if there is an RKE2/k3s cluster rely on it
Remove harvester cluster if there is an RKE2/k3s cluster rely on it