Skip to content
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]: Job Status issues #362

Open
madejackson opened this issue Dec 16, 2024 · 0 comments
Open

[BUG]: Job Status issues #362

madejackson opened this issue Dec 16, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@madejackson
Copy link
Contributor

madejackson commented Dec 16, 2024

What happened?

Leaving this here for tracking. There are 2x related issues with Job statuses:

  1. Status after update: After an update, the last run of a job isn't retained.
  2. When there is an update available and automatic updates are enabled, cosmos updates / restarts itself automatically despite a running job. After restart, the job status is "stopped" and logs cleared. In fact, the Job is still running though and new log entries are still tracked/shown in cosmos.

I have a job which calls a script called mover.sh configured. The job is still running and it still puts out logs.

grafik
grafik

What should have happened?

  • Logs and Last run status should be retained in case of cosmos-update.
  • automatic cosmos update should check for running jobs and delay its update.

System details

  • OS: Debian Bookworm
  • Browser: Firefox
  • Version: 0.17.0 docker-free
@madejackson madejackson added the bug Something isn't working label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant