跳转到主内容

由于未删除PV的ONTAP 卷、PVC挂起

Views:
3
Visibility:
Public
Votes:
0
Category:
astra_trident<a>用于翻译</a>
Specialty:
snapx
Last Updated:

适用场景

适用于 Kubernetes /OpenShift 的 Trident

问题描述

在创建Kubernetes或Trident Snapshot之后、要用于另一个Pod的Kubernetes PVC克隆
、终止原始Pod并删除其PVC不会完全清除Trident中的PV信息。

由于克隆繁忙的Snapshot至少显示两个错误、删除操作失败:
  1. type: 'Warning' reason: 'VolumeFailedDelete' persistentvolume pvc-UUID is still attached to node WORKER_NODE
  2. API status: failed, Reason: Failed to delete volume \"trident_PREFIX_pvc_UUID\" in Vserver \"VSERVER\"because it has one or more clones.\n\nUse the \"volume clone show -parent-vserver VSERVER -parent-volume trident_PREFIX_pvc_UUID\" command to list clones, and either delete or split the clones and retry the operation.\n\nUse \"volume clone split start -vserver \u003cvserver name\u003e -flexclone \u003cclone name\u003e\" to split clones.\nUse \"volume delete -vserver \u003cvserver name\u003e -volume \u003cclone name\u003e\" to delete clones., Code 15894","level":"error","message":"Unable to delete volume from backend."

此外、PVC在输出"oc|kubectl get pvc -o wide"中显示为已释放。

 

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.