Closed BenTheElder closed 2 years ago
This looks a duplicate of https://github.com/kubernetes/kubernetes/issues/96803
/sig api-machinery (based on sig of above references issue)
/assign @lavalamp /triage accepted
https://github.com/kubernetes/kubernetes/issues/96803 had some different failures I think, commented there as well
My guess is we somehow have a race with the apiserver loading the new PL / FS.
spotted again 1.20
seems to be sporadic in HEAD and 1.20 at least: https://storage.googleapis.com/k8s-gubernator/triage/index.html?pr=1&text=matching%20user%20doesnt%20received
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
/remove-lifecycle stale
These are still occurring. We have multiple instances today like:
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/apimachinery/flowcontrol.go:48
May 21 13:27:41.970: matching user doesnt received UID for the testing priority-level and flow-schema
/home/prow/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/onsi/ginkgo/internal/leafnodes/runner.go:113
The failures appear to be only from 1.20. The code for the test is definitely very different now. Probably https://github.com/kubernetes/kubernetes/pull/96984 fixed the problem. I can't think of a reason not to backport it.
Good catch re: 1.20
filed https://github.com/kubernetes/kubernetes/pull/102709, there were conflicts and I'm not certain yet that it's correct.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
What happened:
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/97447/pull-kubernetes-e2e-kind/1342023270328700928
What you expected to happen:
This test should not flake and the logs should show me what did happen.
https://github.com/kubernetes/kubernetes/blob/88a05df5ff1b311e8e92f64b4f3a2c7d4329d14e/test/e2e/apimachinery/flowcontrol.go#L63
How to reproduce it (as minimally and precisely as possible):
Send a PR to Kubernetes. Run tests repeatedly. Enjoy flakes.
Anything else we need to know?:
Environment:
kubectl version
):cat /etc/os-release
):uname -a
):