Skip to main content
NetApp Knowledge Base

Trident volumes stuck in deleting state after OpenShift Virtualization VM deletion

  1. Last updated
  2. Save as PDF
Views:
335
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
astra
Last Updated:

Applies to

  • NetApp Trident 26.xx
  • OpenShift Container Platform (OCP) 4.x
  • OpenShift Virtualization (OCP Virt) 4.x

Issue

After deleting a virtual machine (VM) in OpenShift Virtualization, one or more Trident PVCs remain stuck in volumeState=deleting indefinitely and are never reclaimed.
  • tridentctl get volumes -n trident shows volumes in deleting state that do not progress.
  • Trident controller logs contain:
    • level=warning msg="Backend update resulted in an orphaned volume." backend=<backend-name> vol.Config.InternalName=trident_<backend>_pvc_<uuid> volume=pvc-<uuid> workflow="cr=reconcile"
    • Tridentlevel=debug msg="Updating an existing volume."  volume=pvc-<uuid> volumeState=deleting volume_orphaned=true workflow="cr=reconcile"
    • level=debug msg="Attempting snapshot delete."backend=<backend-name> snapshotName=snapshot-<uuid> volumeName=pvc-<uuid>
      workflow="snapshot=delete"
    • level=warning msg="Retried locked snapshot delete, clone split timer not yet expired." logLayer=core requestID=<id> requestSource=CSI secondsBeforeSplit=86366.62 snapshot=pvc-<uuid>
  • VolumeSnapshot objects (vmsnapshot-*) remain in the namespace after VM deletion.
  • In environments with high VM creation rates, Trident controller performance may also degrade (slow tridentctl responses, timeouts).

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.