メインコンテンツまでスキップ

Trident がバックエンドから Snapshot を削除できないため、 PVC の終了時にハングしています

Views:
2
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

環境

( Astra ) Kubernetes / OpenShift 向け Trident

問題

Trident が PV ボリュームのスナップショットを削除しようとしたときに、次のエラーが発生してボリュームを削除できます。
time="DATE_TIME" level=info msg="Determined topology labels for node: map[]" node=K8S_NODE_N requestID=REQ_UUID requestSource=REST
time="DATE_TIME" level=error msg="Could not begin splitting clone from snapshot."
    cloneVolumeName=CLONED_VOL_PVC_NAME
    error="error splitting clone: API status: failed,
    Reason: This volume cannot be split as it is configured for protection using Vserver level snapmirror.
        Change the protection type using \"volume modify\" command to make it unprotected., Code: 13001"
    parentVolumeName=ORIGINAL_VOL_PVC_NAME requestID=REQ_UUID
    requestSource=CSI   snapshotName=snapshot-UUID
time="DATE_TIME" level=error msg="Unable to delete snapshot from backend." backend=BACKEND_NAME
    error="snapshot snapshot-UUID backing volume PREFIX_ORIGINAL_PVC_NAME is busy" requestID=REQ_UUID
    requestSource=CSI snapshot=snapshot-UUID   volume=ORIGINAL_PVC_NAME

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

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device