Skip to main content
NetApp Knowledge Base

Volumes are not automatically detached even after the attached node is deleted

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

Applies to

  • Trident 21.10.1
  • Kubernetes 1.22.5
  • Node to which the volumes are attached is deleted

Issue

  • VolumeAttachment object is still attached to the deleted node
  • Pod gets stuck in the ContainerCreating state because VolumeAttachment fails by the following error:

rpc error: code = NotFound desc = node <DELETED_NODE> was not found

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.