-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.17
-
No
-
OpenShift SPLAT - Sprint 254, OpenShift SPLAT - Sprint 255
-
2
-
False
-
-
Release Note Not Required
-
In Progress
This is a clone of issue OCPBUGS-33410. The following is the description of the original issue:
—
Description of problem:
for ipi on vSphere. enable capi in installer and install the cluster.after destroy the cluster, according to the destroy log: it display "all folder deleted". but actually the cluster folder still exists in vSphere Client. example: 05-08 20:24:38.765 level=debug msg=Delete Folder*05-08 20:24:40.649* level=debug msg=All folders deleted*05-08 20:24:40.649* level=debug msg=Delete StoragePolicy=openshift-storage-policy-wwei-0429g-fdwqc*05-08 20:24:41.576* level=info msg=Destroyed StoragePolicy=openshift-storage-policy-wwei-0429g-fdwqc*05-08 20:24:41.576* level=debug msg=Delete Tag=wwei-0429g-fdwqc*05-08 20:24:43.463* level=info msg=Deleted Tag=wwei-0429g-fdwqc*05-08 20:24:43.463* level=debug msg=Delete TagCategory=openshift-wwei-0429g-fdwqc*05-08 20:24:44.825* level=info msg=Deleted TagCategory=openshift-wwei-0429g-fdwqc govc ls /DEVQEdatacenter/vm |grep wwei-0429g-fdwqc/DEVQEdatacenter/vm/wwei-0429g-fdwqc
Version-Release number of selected component (if applicable):
4.16.0-0.nightly-2024-05-07-025557
How reproducible:
destroy a the cluster with capi
Steps to Reproduce:
1.install cluster with capi 2.destroy cluster and check cluster folder in vSphere client
Actual results:
cluster folder still exists.
Expected results:
cluster folder should not exists in vSphere client after successful destroy.
Additional info:
- clones
-
OCPBUGS-33410 vsphere - The folder is not deleted after successfully destroying the capi cluster.
- Closed
- is blocked by
-
OCPBUGS-33410 vsphere - The folder is not deleted after successfully destroying the capi cluster.
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update