Bug #32203
closed
Set Timeout to kill settings for ansible runner process explicitly
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1931489
Description of problem:
When executing an Ansible playbook via Satellite job scheduler, the "Timeout to kill" setting is not honored.
I did a test using the "pause" module to make playbook last for 5 min:
---
- hosts: all
tasks:
- name: Pause for 5 minutes
pause:
minutes: 5
and by setting the "timeout to kill" to 30 seconds, it should have terminated the job after 30 sec but it ran for the planned 5 min.
Doing the same with a remote command (to execute a shell script hosted on the target) is killed as expected
1: Timeout for execution passed, trying to stop the job
2: Exit status: TERM
Version-Release number of selected component (if applicable):
6.8.3 (6.6 as well)
How reproducible:
Create a playbook which last quite some time and set a "Timeout to kill" shorter
Steps to Reproduce:
1.
2.
3.
Actual results:
- Ansible playbook continues to run after the "Timeout to kill" period.
Expected results:
- Ansible playbook should be killed after the "Timeout to kill" period.
Additional info:
Updated by Ondřej Ezr almost 3 years ago
- Subject changed from Timeout to kill settings in job execution is not honored when running an Ansible playbook to Set Timeout to kill settings for ansible runner process explicitly
- Triaged changed from No to Yes
Updated by The Foreman Bot almost 3 years ago
- Status changed from New to Ready For Testing
- Assignee set to yifat makias
- Pull request https://github.com/theforeman/foreman_ansible/pull/422 added
Updated by The Foreman Bot almost 3 years ago
- Pull request https://github.com/theforeman/smart_proxy_ansible/pull/41 added
Updated by The Foreman Bot almost 3 years ago
- Fixed in Releases smart_proxy_ansible-3.3.0 added
Updated by yifat makias almost 3 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset smart_proxy_ansible|d9ec4769cf1c127e64dc17d1201449b49f22f8f0.