-
Notifications
You must be signed in to change notification settings - Fork 125
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
Checking batch job status fails #456
Comments
I have the same problem, levant marks deployment as failed because it checks job status, which can be |
hi, same issue .. I have a one-shot container which creates files and then exit 0 .. but pipeline is marked as failed:
cu denny |
You can check status of allocation via cli. It works for checking until it won't be fixed |
Via levant or via Nomad Cli ? Can you give me an example? It sounds for me, that I then need to add an exit 0 and check the state on a separate task. |
|
Also I missed checking while job is running, just add while loop before checking status "complete" |
I have batch job that perform some one-time short-running task. Successfull deploument looks like:
Today i'v got error:
In successful deployment time between "levant/job_status_checker: running job status checker for job" and first status is 0 seconds.
In failed - 4 seconds. During this time my job was successfully finished and has status 'dead' but levant thinks that this task is just dead so it exited with non zero code and fails by CI pipeline.
As i see, levant have some problems with communication to nomad and its tooks to long time to get job status.
Is it possible to disable check of job? because asynchronous checking of short lived tasks may fail unexpectedly
The text was updated successfully, but these errors were encountered: