-
Notifications
You must be signed in to change notification settings - Fork 152
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
Add test for filesystem expansion after snapshot restore / clone #325
Comments
Idea:
The comparison must be tolerant to rounding errors or some growth of the filesystem metadata. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
As described in container-storage-interface/spec#452, CSI driver should resize filesystem on a volume when restoring a snapshot / cloning a volume to a bigger volume.
csi-test
should test this behavior. The test should be optional, at least initially, because we expect a lot of drivers to fail this check.The text was updated successfully, but these errors were encountered: