-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
[CI] testExpiredTokensDeletedAfterExpiration fails in assertBusy #37063
Comments
Pinging @elastic/es-security |
Another failure.
In this case it seems to be caused by scenario 1, but it doesn't reproduce.
|
I got it to reproduce "consistently" (after 4-8 consecutive runs with Line 65 in 265fdce
doesn't get executed before the subsequent search request in the test at Line 152 in 0cae979
but that would be taken care of by the retries in the assertBusy block. It turns out that the issue is with Line 1076 in 0cae979
and the fact that we submit an invalidation request also a little further up on the same test. This has the effect that the two invalidation requests are executed with ~1s interval and as the This manifests now as we removed the bwc invalidation logic and this made the invalidation duration much shorter What doesn't fit with this theory is the
that was seen in CI as the only way to get an
I adjusted this and it didn't make a difference but this is a very good suggestion regardless of the issue at hand. I adjusted the |
This test failed on (edited by @jkakavas to add formatting)
I'm reopening this issue to raise your attention @jkakavas (maybe just a fix to backport?) since I muted the test on 6.7 in 0002203 |
We run subsequent token invalidation requests and we still want to trigger the deletion of expired tokens so we need to lower the deleteInterval parameter significantly. Especially now that the bwc expiration logic is removed and the invalidation process is much shorter Resolves #37063
We run subsequent token invalidation requests and we still want to trigger the deletion of expired tokens so we need to lower the deleteInterval parameter significantly. Especially now that the bwc expiration logic is removed and the invalidation process is much shorter Resolves #37063
From https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+corretto-periodic/ES_BUILD_JAVA=openjdk12,label=amazon/27/console
Does not reproduce.
I have a couple of ideas about what could cause this:
securityClient.prepareInvalidateToken("fooobar")
fails in an unexpected way then that exception will occur inside theassertBusy
and not stop the test, but it might mean that the token removed was never started. I don't see any evidence of that in the logs though.The text was updated successfully, but these errors were encountered: