-
Notifications
You must be signed in to change notification settings - Fork 39.3k
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
[Flaking Test] ci-kubernetes-unit (Unexpected event resourceVersion 2 less than or equal to bookmark 2) #125244
Comments
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
/sig storage |
/sig api-machinery |
This started last week, but it seems to be fairly rare, so might be a consequence of something a bit earlier. The value of "2" suggests that it's happening on the first event, and my brain goes towards: https://github.com/kubernetes/kubernetes/pull/124754/files @p0lyn0mial - will you be able to take a look at it? |
sure, I will have a look. /assign @p0lyn0mial |
We chatted with @p0lyn0mial about that offline and it seems like a real correctness issue. Regression indeed introduced by https://github.com/kubernetes/kubernetes/pull/124754/files We have a race with setting RV in watchcache and incoming events. The current explanation is:
|
@wojtek-t @p0lyn0mial So it is a release blocker, then? (Upcoming alpha 1 release cut scheduled for tomorrow) |
I don't know what the release policy is but we might have a potential fix for this issue. |
This is a real correctness bug introduced 2 weeks ago. I'm not sure what's our policy is for alpha releases, but it sounds like a potential blocker to me. |
The fix for it is already approved. |
Which jobs are flaking?
sig-release-master-blocking
Which tests are flaking?
k8s.io/apiserver/pkg/storage/cacher.cacher
Since when has it been flaking?
05/30/2024 19:25 IST
Prow Logs: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-unit/1796177771727163392
Triage: https://storage.googleapis.com/k8s-triage/index.html?test=k8s.io%2Fapiserver%2Fpkg%2Fstorage%2Fcacher.cacher
Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#ci-kubernetes-unit
Reason for failure (if possible)
Anything else we need to know?
No response
Relevant SIG(s)
/sig
The text was updated successfully, but these errors were encountered: