Description of problem: The backend vmdk gets deleted automatically without any action. While checking PV and PVC are in bound state . Checking at the vmware side shows openshift user is deleting the vmdk Version-Release number of selected component (if applicable): 4.6.42 Actual results: VMDK getting deleted Expected results: VMDK should not be deleted Master Log: Sharing link to all the logs
From the support ticket: > What we need to understand is why OpenShift is trying to delete the volume *afterwards*, when it was already deleted, and how to stop/clean this requests. User has deleted PVC. Kubernetes tries to delete PV + the volume in storage backend, but it's already gone and here is a bug in the Kubernetes code - it should treat "vmdk not found" as a *successful deletion*. This has been fixed in 4.9: https://github.com/kubernetes/kubernetes/pull/92372. If you want Kubernetes to stop, delete the PV manually.