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 possible race of listwatch in admission test #113760
fix possible race of listwatch in admission test #113760
Conversation
65ce5df
to
f383dfc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this!
staging/src/k8s.io/apiserver/pkg/admission/plugin/cel/admission_test.go
Outdated
Show resolved
Hide resolved
f383dfc
to
4e21715
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexzielenski, logicalhan 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 |
test-only change to deflake a test, so adding to milestone ahead of 1.26 test freeze |
/triage accepted |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Fixes a race in test code caused by the fact that the fake object tracker does not respect the lastSyncedResource version option when a watch Is started, so any objects added by a test between the list and watch of the informers might be dropped.
This change creates a noop policy bindings and policy definitions and keeps updating them until the update is noticed by the controller, to show that watch is established. Then the test is allowed to continue.
This bug was reproduced using the
stress
tool with-race
. It occurred on my machine about 0.05% of the time. After this change there are failures 0% of the time measured usingstress
.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/cc @jpbetz @logicalhan