Bug #35905
closedtime to pickup kills long running pull jobs, timeout to kill doesn't work in the same scenario
Description
Description of problem:
For pull-mqtt rex jobs, the "time to pickup" kills a long running job, so it behaves like the "timeout to kill" setting. In the same scenario, timeout to kill does not kill a long running pull-mqtt job
Version-Release number of selected component (if applicable):
Satellite 6.13 snap 5
How reproducible:
always
Steps to Reproduce:
1. have a satellite with pull-mqtt rex mode and a registered host with mqtt client
2. Prepare a command job that will execute for some time, e.g: "echo start; sleep 60s; echo done"
3. In rex wizard, set "time to pickup" to 20s
4. Run job
Actual results:
The job fails after 20s with Proxy error: RuntimeError - The job was not picked up in time.
Furthermore, using "timeout to kill" in step 3 above doesn't result in stopping the job.
Expected results:
Time to pickup should distinguish between "not picked yet" and "already running" states. Timeout to kill should work on pull jobs as expected
Additional info:
Confirmed that timeout to kill works correctly in non-pull scenarios
Updated by The Foreman Bot over 1 year ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/99 added
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases smart_proxy_remote_execution_ssh-0.10.0 added
Updated by Adam Ruzicka over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_proxy_plugin|faa269652c7973ce5a04a4b2945dcd2bcd203505.
Updated by Adam Ruzicka over 1 year ago
- Fixed in Releases smart_proxy_remote_execution_ssh-0.10.1 added
- Fixed in Releases deleted (
smart_proxy_remote_execution_ssh-0.10.0)