-
Notifications
You must be signed in to change notification settings - Fork 379
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
VolumeGroupSnapshot deletion intermediate failures #1035
Comments
This is also fixed by #1011 as this updates the volumegroupsnapshotname in the snapshotcontent status |
It looks like not fixed yet, reopening |
Hello, I'm having some difficulty understanding the detail of this issue. Would this issue present itself by failing to delete a snapshot or would it somehow accidentally delete a snapshot. Would somebody be so kind enough to explain? Thanks! |
@jedops the snapshots are deleted internally when the volumegroupsnapshot are deleted, i have provided steps to reproduce and some logs as well, you can see some checks are missing to skip already deleted snapshots or we need reorder the steps on how we delete snapshot which are created as part of volumegroupsnapshot. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Just an update, I tested the creation of deletion of volumegroupsnapshot with cephfs driver and it seems to work fine.
|
Just an update, I tried out the same with 10-11 pvcs, the volumegroupsnapshot was successfully deleted.
cc @Madhu-1 |
good to hear we dont have this bug anymore, in that case we can close it. |
@Madhu can you please close this issue as well. |
@Madhu-1 can you re-open this issue, we can use the same issue to track the bug |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Can you still reproduce this problem? A snapshot content can't be deleted if the group snapshot handle is in its status. How did you clear the status? |
we were able to reproduce this is in one of our DR cluster, will share the output with you, currently the cluster is destroyed. |
After reproducing this error with correct version of snapshotter, we were not able to reproduce this error. So, I think we are good to close this issue. |
What happened:
The volumegroupsnapshot deletion is kind of stuck because the volumesnapshotcontent are already deleted
external-snapshotter/pkg/sidecar-controller/groupsnapshot_helper.go
Lines 242 to 249 in fcf78d3
What you expected to happen:
The volumegroupsnapshot deletion should happen
How to reproduce it:
It's sometimes happens not always
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):Logs
The text was updated successfully, but these errors were encountered: