Bug 2028112 - Ansible roles are failed with exit status 0 but the job is showing status success and the task is also showing result success.
Summary: Ansible roles are failed with exit status 0 but the job is showing status suc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible - Configuration Management
Version: 6.9.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.12.0
Assignee: satellite6-bugs
QA Contact: Sam Bible
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-01 13:54 UTC by Gourav Padholia
Modified: 2022-11-16 13:33 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-smart_proxy_ansible-3.4.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:33:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-13533 0 None None None 2022-10-21 15:34:49 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:33:17 UTC

Description Gourav Padholia 2021-12-01 13:54:11 UTC
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:

Comment 1 Adam Ruzicka 2022-06-07 14:15:52 UTC
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"

Comment 5 Sam Bible 2022-08-16 17:27:37 UTC
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.

Comment 9 errata-xmlrpc 2022-11-16 13:33:03 UTC
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


Note You need to log in before you can comment on or make changes to this bug.