-
-
Notifications
You must be signed in to change notification settings - Fork 0
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]: Kubernetes build status fetch error on server restart #562
Comments
This error is strange since Kubernetes job should not be removed directly. We might define a duration after which the job is failed at the server start. use the same duration as build timeout. |
Check if the deployment timeout covers this issue |
I don't think that this is a problem with Kubernetes because if you go to the This means that only the Kubernetes.Status GenServer crashed or stopped prematurely and that we just need to ignore the error on the server when trying to stop this GenServer when it is not running. Please see my PR to fix this issue, and don't hesitate to read the PR description for more information. |
What happened?
When the server restart, it try to get back the build status to complete de build. But if the build didn't exist anymore on the kubernetes because it's finished (But notification didn't got retrieved by the server) the server throw an error at start for each build.
What browsers are you seeing the problem on?
No response
Version
1.5.3
Relevant log output
https://lenra-br.sentry.io/issues/4573629917/
The text was updated successfully, but these errors were encountered: