node still shows as Running on Killed job

[Alexander Szele]

Unclear if there is a way to resolve this or if it's a current known bug in Rundeck. We were on v5.14.0 preparing to upgrade to 5.15.0. We had a job that was stuck in a Running state because the server had been rebooted while a job was running. This usually leaves jobs in a perma-stuck state as they lose the connection to the endpoint they were running against.

We killed the job, but now single node that the job was running against still shows as status "Running" despite the job being aborted. While this is probably little more than a cosmetic issue, we'd like to know if there's anything to be done to terminate the job status on the node.

Thanks!

Alex Szele

[rac...@rundeck.com]

Hi Alexandre,

Please, take a look at this.

Regards!

[Alexander Szele]

I appreciate the reference but that is discussing a situation where the JOB is incomplete or stuck in a running status. In this case the job shows status incomplete/aborted, but there is a single node associated with the job execution that still shows status Running.