Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJoniel Pasqualetto
2022-08-15 21:09:28 UTC
Description of problem:
Going to a host and running ansible roles returns success on the tasks even if the task ansible execution finished with errors.
Example of failed task that returned and "exit status" of 0:
~~~
(...)
}
143:
}
144:
145:
TASK [Apply roles] *************************************************************
146:
ERROR! the role 'RedHatInsights.insights-client' was not found in /tmp/d20220815-1121-f1vuvr/project/roles:/etc/ansible/roles:/usr/share/ansible/roles:/tmp/d20220815-1121-f1vuvr/project
147:
PLAY RECAP *********************************************************************
148:
rhel7-test : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
149:
Exit status: 0
~~~
Running the same job manually, returns same error and exit code is 2:
~~~
/usr/bin/ansible-runner run /tmp/d20220815-1121-4sokh0 -p playbook.yml
(...)
TASK [Apply roles] *************************************************************
ERROR! the role 'RedHatInsights.insights-client' was not found in /tmp/d20220815-1121-4sokh0/project/roles:/root/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/tmp/d20220815-1121-4sokh0/project
PLAY RECAP *********************************************************************
rhel7-03123217 : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
# echo $?
2
~~~
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Associate any role to a host
2. Delete the role from the filesystem to force it to break (in my example I associated role RedHatInsights.insights-client and the removed it from /usr/share/ansible/roles/
3. Try running the job to "Run Ansible Roles" on the host.
Actual results:
Return success
Expected results:
Return the actual exit code from ansible
Additional info:
Comment 3Joniel Pasqualetto
2022-08-17 15:09:57 UTC
*** This bug has been marked as a duplicate of bug 2107577 ***
Description of problem: Going to a host and running ansible roles returns success on the tasks even if the task ansible execution finished with errors. Example of failed task that returned and "exit status" of 0: ~~~ (...) } 143: } 144: 145: TASK [Apply roles] ************************************************************* 146: ERROR! the role 'RedHatInsights.insights-client' was not found in /tmp/d20220815-1121-f1vuvr/project/roles:/etc/ansible/roles:/usr/share/ansible/roles:/tmp/d20220815-1121-f1vuvr/project 147: PLAY RECAP ********************************************************************* 148: rhel7-test : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 149: Exit status: 0 ~~~ Running the same job manually, returns same error and exit code is 2: ~~~ /usr/bin/ansible-runner run /tmp/d20220815-1121-4sokh0 -p playbook.yml (...) TASK [Apply roles] ************************************************************* ERROR! the role 'RedHatInsights.insights-client' was not found in /tmp/d20220815-1121-4sokh0/project/roles:/root/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/tmp/d20220815-1121-4sokh0/project PLAY RECAP ********************************************************************* rhel7-03123217 : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 # echo $? 2 ~~~ Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Associate any role to a host 2. Delete the role from the filesystem to force it to break (in my example I associated role RedHatInsights.insights-client and the removed it from /usr/share/ansible/roles/ 3. Try running the job to "Run Ansible Roles" on the host. Actual results: Return success Expected results: Return the actual exit code from ansible Additional info: