-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
stream, 6.16.0, 6.17.0
-
False
-
Important
-
sat-endeavour
-
None
-
None
-
None
-
None
Description of problem:
timeout_to_kill setting doesn't take effect on ssh jobs
How reproducible:
always
Is this issue a regression from an earlier version:
seems to be around for quite some time
Steps to Reproduce:
- run job with timeout to kill setting set, for example run command job with 'for run in {1..160}; do sleep 1; echo ${run}; done' and set timeout to 5s
- check the host console
Actual behavior:
"Timeout for execution passed, trying to stop the job" shows up in the console but the job is not killed and the original command continues to execute
Expected behavior:
job is killed when the timeout is reached
Business Impact / Additional info:
automation
pytest tests/foreman/cli/test_remoteexecution.py::TestRemoteExecution::test_positive_timeout_to_kill[rhel9-ipv4]