-
Notifications
You must be signed in to change notification settings - Fork 386
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
bug/flake: TestAPIExportAuthorizers - APIExport view missing queueing for related APIExports (via claims) #2713
Comments
I can reproduce this locally. I've added extra logging to kcp/pkg/virtual/apiexport/controllers/apireconciler/apiexport_apireconciler_reconcile.go Line 134 in 6124312
sometimes returns 0 exports, meaning kcp can't find the APIExport for |
By any chance, is this flake the same as what @jmprusi seemed to have tried to fix in PR https://github.com/kcp-dev/kcp/pull/2417/files#diff-8d6f5573691c6741b1615098ed0f51a30afa2e1e9a906f19d5cbfceaef754930 ? |
@davidfestal yes, although that's not really a fix 😄 |
More data from a local test failure (sharded, 1 shard):
|
Note: the APIExport informer here is from the cache server |
Oh I think when the APIExport that has sheriffs gets updated, we need to queue all other APIExports that have claims against its (sheriffs) identity. Testing this out. |
Root cause:
|
reopening as I ran into this flake today: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/kcp-dev_kcp/2423/pull-ci-kcp-dev-kcp-main-e2e-sharded/1620860539901054976 |
Different root cause. Let's open a new one. |
@ncdc: Closing this issue. In response to this:
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. |
#2732 for the new one |
From https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/kcp-dev_kcp/2707/pull-ci-kcp-dev-kcp-main-e2e-sharded/1620426348143054848 for PR #2707
The text was updated successfully, but these errors were encountered: