Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2033163

Summary:	VMDK deleted automatically
Product:	OpenShift Container Platform	Reporter:	Sonigra Saurab <ssonigra>
Component:	Storage	Assignee:	Jan Safranek <jsafrane>
Storage sub component:	Kubernetes External Components	QA Contact:	Wei Duan <wduan>
Status:	CLOSED INSUFFICIENT_DATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	aos-bugs, jsafrane
Version:	4.8
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-02-07 15:50:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sonigra Saurab 2021-12-16 05:10:54 UTC

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

Comment 8 Jan Safranek 2022-01-25 14:50:01 UTC

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.