Various tests stayed 'running' for ~ 4 hours or longer
it was a clone of an earlier one, that finished incomplete.
The restarted job staid around for 4 hours, but did not really make progress (and the test usually finishes much quicker. normaly runtime of RAID10/TW is 30 - 45 minutes)
Updated by okurz over 4 years ago
- Subject changed from Various tests stayed 'running' for ~ 4 hours to Various tests stayed 'running' for ~ 4 hours or longer
Let me hijack this ticket to reference most recent examples on OSD which run for > 6 days (!):
All of them have been cloned to newer jobs already and they do not even block the workers anymore as the assigned worker already executed other jobs just fine. Cancelling the job over web UI does not work, restarting the worker instance systemd job also not successful. A manual deletion of the job does work but I haven't executed that on theabove jobs, just an older one last week.