-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trident snapshot objects not deleted with deletionPolicy Retain #462
Comments
Hi @gnarl, Any update on this? |
This issue has a more pronounced effect on Element OS (probably E-Series too) because the maximum number of snapshots on these platforms is lower than ONTAP: while on ONTAP the "only" problem is leftover snapshots, on Element OS snapshot protection stops working because without automated expiration the maximum number of snapshots is reached within days. |
I think the problem here is the volumeSnapshotContent has the deletionPolicy of "Retain" and it should be updated to "Delete" prior to deleting the volumeSnapshot and volumeSnapshotConent if the goal is to actually delete the snapshot. This is different than how deleting a PV with the reclaimPolicy set to "Retain" works. In that case, K8S forces you to set edit the PV and change the reclaimPolicy to "Delete" before you can successfully delete the PV. I'll talk to the team about how to handle this use case. |
@khankth when deleting a snapshot with
In addition, the other error you have pointed out [ |
FAILURE SCENARIO
a. Tridentctl get snapshot list shows the snapshot in the list
b. Tridentctl get snapshot throws error:
tctl get snapshot snapshot-abb03b32-432c-4c63-b550-a571050b787e
c. Tridentctl delete snapshot throws error:
If this is a bug please look into it, otherwise, this is causing alot of leftover snapshot objects in the trident. Please provide instructions/guidance now on how to remove the trident snapshot objects with the deletePolicy is Retain?
SUCCESS SCENARIO
Trident Snapshot objects are successfully deleted with deletionRetain: Delete
In this case they are auto-removed after deletion of volumesnapshots.snapshot.storage.k8s.io
Environment
Provide accurate information about the environment to help us reproduce the issue.
The text was updated successfully, but these errors were encountered: