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.

Description of problem:
Ansible roles from the Satellite server is failed and showed the exit status 0 but the ansible job and the task is showing success. 

Version-Release number of selected component (if applicable):
Satellite 6.9

How reproducible:
100 %

Steps to Reproduce:
1. Create a few roles on the Satellite server. Give the name RH1, RH2, RH3. 
2. The tasks/main.yml file of the role "RH1" will include other roles RH2 and RH3. 
3. Roles RH2 and RH3 have a playbook(main.yml) to install the package on the client. 
4. Import the roles in the Satellite server and add role A on the host. 
5. Run role A on the host. This task will fail with exit_status 0. But the job is showing success. 

Actual results:
The remote jobs and the Satellite task is showing the result success. 

Expected results:
The task should show the error since the job is failed for some reason.  

Additional info:

This could be fixed in smart_proxy_ansible-3.3.1 (Sat 6.10+) by https://projects.theforeman.org/issues/34395 . I'll need to double check this before doing the flag dance, but for now let's roll with "there's a chance this is already fixed"

Version-Release number of selected component (if applicable):
Satellite 6.12 - 6

Steps to Reproduce:
1. Import the roles as mentioned above by Adam to Satellite
2. Add Role A onto the Host.
3. Run role A on the host

Actual results:
The Job fails, and the task on Satellite also fails and show the error. 

Expected results:
The task should show the error since the job is failed for some reason.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:8506