-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Error: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline #7991
Comments
Please share more details:
|
We are on velero 1.13. Attaching the velero log file. |
Looks like the wait retry mechanism which hits a timeout cause the client-go generates an unexpected error (see here):
|
Hi @Lyndon-Li , anyway we have the default timeout of 10min and the polling at an interval of 5 sec, from the logs we can see that the polling succeeded after 2-3 retries, so I don't think we hit timeout here over here. |
This issue may relate to #7978. |
@blackpiglet can you help explain why you think they might be correlated? |
IMO, this error means the client failed to get the VolumeSnapshot in the time limitation of the go-client. |
Hi, any update on this issue? I seem to be dealing with the same issue on v1.14.0:
|
In our case, we get hit by this issue because of Azure/AKS#4555 |
@curtis-baillie |
We already do. |
@monotek |
Sorry, we already removed Velero now and do our volume snapshots by an own controller. |
What steps did you take and what happened:
There are bunch of clusters where the backup of snapshots are failing with the following error:
**What did you expect to happen: **
Cluster seems to be healthy; we are not seeing any issue related to pod crunch or Api server in the timeframe when this error occurred.
The following information will help us better understand what's going on:
Found a related GitHub issues: https://github.com/helm/helm/issues/12154
Error is getting thrown at this Code Path: https://github.com/kubernetes/client-go/blob/354ed1bc9f1f48c820fdc5e84b566acfd716cf42/rest/request.go#L619
If you are using velero v1.7.0+:
Please use
velero debug --backup <backupname> --restore <restorename>
to generate the support bundle, and attach to this issue, more options please refer tovelero debug --help
If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velero
velero backup describe <backupname>
orkubectl get backup/<backupname> -n velero -o yaml
velero backup logs <backupname>
velero restore describe <restorename>
orkubectl get restore/<restorename> -n velero -o yaml
velero restore logs <restorename>
Anything else you would like to add:
Environment:
velero version
):velero client config get features
):kubectl version
):/etc/os-release
):Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: