-
Notifications
You must be signed in to change notification settings - Fork 34
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
CreateVolume times out and controller gets stuck in already exists loop #12
Comments
Seems like it's probably related to this: kubernetes-csi/external-provisioner#131 |
@damomurf thanks for reporting it, and details about the issue. It really helps to find what to update. It should be an easy fix. I'll post a comment when the driver is updated. (also, sorry for late response, somewhat notification is not working.. I didn't get any email from github..) |
#12: Use existing LUN if LUN exists in createVolume to handle retry
@damomurf I've updated the code & docker image. Please try with the new docker image, and let me know if it still does not work for you. |
Thanks for your work on this!
I think the provisioning of my LUN/Target is taking longer than some hard-coded 10 second timeout.
Once the timeout occurs, the controller continues trying to create the same objects on the Synology, but constantly just receives the already exists error.
I feel like there should be better handling of the timeout case and would it be possible to make the timeout interval configurable?
The text was updated successfully, but these errors were encountered: