Skip to content
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

Closed
aayush-rangwala opened this issue Jun 27, 2020 · 5 comments
Closed

csi-snapshotter pod throws an error "volumeID is not exist" #188

aayush-rangwala opened this issue Jun 27, 2020 · 5 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@aayush-rangwala
Copy link

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 accessible

Tried 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 and VolumeSnapshot are correct as per the docs and also It was working some time with the same listed setups and sometime it not

@scuzhanglei
Copy link

scuzhanglei commented Jul 16, 2020

it's because the plugin just keep volumes in memory. same as #55

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 14, 2020
@aayushrangwala
Copy link
Contributor

aayushrangwala commented Nov 7, 2020

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.

@aayushrangwala
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@aayushrangwala: Closing this issue.

In response to this:

/close

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.

TerryHowe pushed a commit to TerryHowe/csi-driver-host-path that referenced this issue Oct 17, 2024
…-notes-docs

SIDECAR_RELEASE_PROCESS.md: Update release-notes syntax
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants