I have a "apt dist-upgrade" job that I ran in Semaphore, which updated docker, which restarted Semaphore (I'm using the docker compose method to run it). I now have a task that is "Running", but there is no Ansible process associated with it.
Looks like if you have any task running and do a restart of Semaphore, it's going to be stuck on that task, presumably indefinitely. Mine has been running 12 hours. Clicking the "Stop" button in the task doesn't seem to do anything.
I'm thinking that at Semaphore startup time it needs to look for any "Running" tasks and clean up anything that is dangling.
I have a "apt dist-upgrade" job that I ran in Semaphore, which updated docker, which restarted Semaphore (I'm using the docker compose method to run it). I now have a task that is "Running", but there is no Ansible process associated with it.
Looks like if you have any task running and do a restart of Semaphore, it's going to be stuck on that task, presumably indefinitely. Mine has been running 12 hours. Clicking the "Stop" button in the task doesn't seem to do anything.
I'm thinking that at Semaphore startup time it needs to look for any "Running" tasks and clean up anything that is dangling.
Created a discussion here: https://github.com/ansible-semaphore/semaphore/discussions/1384