-
Notifications
You must be signed in to change notification settings - Fork 109
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
Volume Snapshots (Clones) Broken on 2.7.0 #628
Comments
Oops, seems like GitHub auto-closed this. @nick-oconnor Thanks for reporting this, we have tried to add fix for the same. Would it be possible for you to test this with a prerelease version before we make a patch release. That would be really helpful as in to understand if this really fixes the issue. |
Hi @Abhinandan-Purkait! Thanks for the fix. Yep, I can test it. Lmk when there's a prerelease ready. |
Thanks @nick-oconnor, you can try with the helm chart as below
|
Looks good 👍
|
Thanks @nick-oconnor, We will do the patch release. Also tracking the automated upgrade testing here #635 |
@nick-oconnor 2.7.1 has been released. Please check and close this issue if it is resolved. Thanks |
Thanks for getting this fixed so quickly! LGTM. |
What steps did you take and what happened:
I use volsync to backup PVCs. After upgrading to 2.7.0, volume snapshot (clone) creation fails. The only error I saw was logged by the node daemonset:
Based on the message, it looks like the
quota
option label is missing from the command (i.e.-o =1073741824
). I'm not setting quota type explicitly. Rolling back to 2.6.2 resolves the issue.What did you expect to happen:
I expected the snapshot to be successfully created.
The output of the following commands will help us better understand what's going on:
I didn't get a chance to grab full logs before rolling back to 2.6.2.
Anything else you would like to add:
Nope.
Environment:
kubectl version
): 1.31.4/etc/os-release
): Ubuntu 24.04.1The text was updated successfully, but these errors were encountered: