-
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
csi-snapshotter pod throws an error "volumeID is not exist" #188
Comments
it's because the plugin just keep volumes in memory. same as #55 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Well actually, issue did not came on 1.4.0. Most probably due to this pr #161 . I guess it is safe to close this issue now. |
/close |
@aayushrangwala: 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. |
…-notes-docs SIDECAR_RELEASE_PROCESS.md: Update release-notes syntax
While trying out the
VolumeSnapshot
, getting the error intermitently:Failed to create snapshot: failed to take snapshot of the volume, pvc-7cf67f78-a5b9-11ea-81ba-42010a8e0fc6: "rpc error: code = Internal desc = volumeID is not exist
where it is definitely sure that the pvc
pvc-7cf67f78-a5b9-11ea-81ba-42010a8e0fc6
exists in the namespace and is accessibleTried to get the logs of csi-snapshotter and csi-hostpathplugin logs, had same errors.
k8s version: 1.14, 1.15, 1.16
CSI versions: 1.2.0, 1.3.0
VolumeSnapshotClass
andVolumeSnapshot
are correct as per the docs and also It was working some time with the same listed setups and sometime it notThe text was updated successfully, but these errors were encountered: