-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Argo server logs print "token not valid for running mode" every 30s #5697
Comments
You most likely have a user who's browser window is open - but they have been logged out. |
it really pollutes the logs. seems like the UI shouldn't need to poll the server if user's logged off. |
Check also if there is a healtcheck from kubernetes |
there's only the readiness probe:
but the frequency of these info-level log lines doesn't suggest it is that. |
I am having the same error time="2021-05-19T04:35:52.989Z" level=info msg="SSO enabled" and here my config |
any one knows this is the problem from the keycloak or argo setup itself? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello, any update on this issue? @avifried1 have you resolved it? |
Hello, we have the same issue with Argo Wfl 3.1.3 TLS and SSO with Keycloak as OIDC provider. |
Hello, for us the issue remains the same, any updates on this? |
I believe this issue happens because the user interface retries on error. This can happen when you were logged in, then login expires. It is either retrying too often, or should stop if the error is Unauthorised. |
@sarabala1979 I've kept this one for @dpadhiar as I think we should fix it. |
@sarabala1979 @dpadhiar going into the details of this, it seem "bombarded" does not mean ever 30ms, but every 30s. I think this is fine for most users and not worthwhile fixing today. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
To fix this:
Add some kind of backoff. |
Signed-off-by: Alex Collins <[email protected]>
Signed-off-by: Alex Collins <[email protected]>
Signed-off-by: Alex Collins <[email protected]>
Summary
The argo server logs are bombarded with the following error every 30s or so:
Running with both SSO & client auth modes. Both work fine in UI & API calls (with authentication header with
Bearer TOKEN
)We haven't seen this before v3 (upgraded from
v2.12.11
).Diagnostics
Running on self-managed k8s cluster in AWS. Server behind an ingress, running insecure with TLS termination done in LB.
Argo workflows
v3.0.1
Server YAML:
SSO:
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: