-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Fix for ResourceQuotaConflictError #5252
Conversation
|
Hi @yachna. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/kind bug |
Shouldn't this already already be handled in pipeline/pkg/reconciler/taskrun/taskrun.go Line 577 in 94055d9
Also see #734 |
Hi @dibyom, we are not facing an exceeded resource quota. We face the problem that when you create a resource (for example a Pod) that is constrained by a resource quota, then the creation can fail because of conflicts while updating the resource quota status (that's the long-standing Kubernetes issue that @yachna mentioned, kubernetes/kubernetes#67761). But maybe that function is where we need to move the retry logic @yachna, with maybe a requeue after one second. |
@SaschaSchwarze0 thanks for the explanation! and yeah, instead of implementing custom retry logic, I think we should catch the error and put it back in the work queue to retry. |
/ok-to-test |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
@dibyom we are ready here, code has been moved :-) |
Thanks @yachna and @SaschaSchwarze0 The code looks fine to me. One request - could we update the commit message with a bit more description around what the issue was that this commit solves (like the description here so that it meets our commit guidelines: https://github.com/tektoncd/community/blob/main/standards.md#commits |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @dibyom Thanks for the suggestion. I have updated the commit message accordingly. |
The following is the coverage report on the affected files.
|
This commit contains fix for the bug ResourceQuotaConflictError More details about the issue are here kubernetes/kubernetes#67761
The following is the coverage report on the affected files.
|
/lgtm |
/test pull-tekton-pipeline-integration-tests |
/retest |
Changes
Fix for the bug ResourceQuotaConflictError kubernetes/kubernetes#67761
From @SaschaSchwarze0
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes