-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
failed to provision volume: context deadline exceeded #8727
Labels
Comments
@stuartpb can you please paste |
can you try with the ceph-csi v3.3 image and see if the issue persists? |
|
can you please try workaround specified at #8696 (comment) |
Closing as duplicate of #8696. please feel free to reopen if it's not. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have two PVCs stuck waiting in the Provisioning state on my cluster. Here are the initial logs from when the rdbplugin-provisioner pod started - the first 9 failures or so coincide with the pool not being available (one of the nodes in my cluster went down during initialization, which may have delayed the pool for a while), but after that, attempts to provision start to fail with "rpc error: code = DeadlineExceeded desc = context deadline exceeded", and then after that, they start to fail with "an operation with the given Volume ID already exists":
After deleting and recreating the provisioner pod, I'm still seeing the same kind of error in the new one:
The text was updated successfully, but these errors were encountered: