Bug 1796660

Summary:	[4.4] duplicate delete commands are seen when deleting PVs backed by vsphere volumes; first call succeeds, second fails with disk not found
Product:	OpenShift Container Platform	Reporter:	milti leonard <mleonard>
Component:	Storage	Assignee:	Hemant Kumar <hekumar>
Status:	CLOSED ERRATA	QA Contact:	Wei Duan <wduan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	andcosta, aos-bugs, chuffman, jsafrane, lxia
Target Milestone:	---
Target Release:	4.4.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1808548 1808549 1808550 1808551 1809781 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:28:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1809781
Bug Blocks:	1808548, 1808551

Description milti leonard 2020-01-30 21:28:11 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0
Build Identifier: 

when deleting a PV that is backed by a vsphere volume (VMDK), the delete command is duplicated; initial delete call will succeed on volume; however the second delete call on the same volume will fail w *vmdk not found* as it has already been deleted and confirmed as deleted in logs. 

customer configuration seems good and this is happening in more than one cluster; each cluster has only one datastore defined.

Reproducible: Didn't try

Steps to Reproduce:
1. configure vsphere datastore for cluster
2. create PV/PVC 
3. delete PVC and then PV


Expected Results:  
after VMDK has been confirmed as deleted; there is no duplicate delete call on the deleted VMDK

the customer has not reported business impact, but their vmware console is flooded with the errors from the failed duplicated delete command; this is not restricted to a single cluster/namespace/node/datastore, but happens everywhere in their environment

customer is using several different storageclasses, but this issue only appears on the storageclass backed by vsphere

Comment 9 errata-xmlrpc 2020-05-04 11:28:24 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581

Comment 10 Red Hat Bugzilla 2024-01-06 04:27:47 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days