Bug #33313
closedRemote execution status is successful for any ansible based jobs even if the actual job execution has failed on the host in Satellite 6.10
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1995661
Description of problem:
Remote execution status is successful for ansible based jobs even if the actual ansible-playbook execution has failed on the host
Version-Release number of selected component (if applicable):
Satellite 6.10
How reproducible:
Always
Steps to Reproduce:
1. Build a Satellite 6.10 and register a host with the satellite
2. Setup REX keys with that host
3. Run any "Ansible COmmand" or "Ansible Playbook" based jobs or "Ansible roles" on the host
Actual results:
Job Result shows 100% success
But if i click on each host entry to see what happened, I could see failures etc.
1:
2:
PLAY [all] *************************************************************
3:
4:
TASK [Gathering Facts] *************************************************
5:
fatal: [host.example.com]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: Could not resolve hostname host.example.com: Name or service not known", "unreachable": true}
6:
PLAY RECAP *************************************************************
7:
host.example.com : ok=0 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0
8:
Exit status: 0
Expected results:
Result should reflect the correct status
Additional info:
The behavior is not observed when using non-ansible type jobs like the "Commands" category.
Updated by The Foreman Bot over 2 years ago
- Status changed from New to Ready For Testing
- Assignee set to Adam Ruzicka
- Pull request https://github.com/theforeman/smart_proxy_ansible/pull/49 added
Updated by The Foreman Bot over 2 years ago
- Pull request https://github.com/theforeman/foreman_ansible/pull/452 added
Updated by The Foreman Bot over 2 years ago
- Fixed in Releases smart_proxy_ansible-3.3.0 added
Updated by Adam Ruzicka over 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset smart_proxy_ansible|9d0680c064cf5f664c889c98a2545fedd8a98096.
Updated by Adam Ruzicka over 2 years ago
- Fixed in Releases foreman_ansible_core-4.1.3 added