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.

Bug 2156532

Summary: Misleading job invocation details when running ansible roles in bulk
Product: Red Hat Satellite Reporter: Jan Senkyrik <jsenkyri>
Component: Ansible - Configuration ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.0CC: nalfassi, torkil, wpinheir
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 12:56:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
job invocation details
none
invocation_all_failed none

Description Jan Senkyrik 2022-12-27 10:44:30 UTC 
Description of problem:
Roles assigned only to host_a show up in host_b job invocation details.

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

Let me explain it on a real example:
- Have 2 hosts - 'jsenkyri-rhel8' and 'jsenkyri-rhel7'
- Assign 'RedHatInsights.insights-client' role to 'jsenkyri-rhel8'
- Do *not* assign any roles to 'jsenkyri-rhel7'
- Select both hosts and hit 'Run all Ansible roles'
- Check job details for 'jsenkyri-rhel7'. Tasks related to 'RedHatInsights.insights-client' role are visible even though the role is *not* assigned to this host. See attached screenshot.

Actual results:
Role(s) assigned *only* to 'jsenkyri-rhel8' show-up in 'jsenkyri-rhel7' job invocation details.

Expected results:
Job invocation details for 'jsenkyri-rhel7' should only show roles/tasks that are assigned to this particular host.
Comment 1 Jan Senkyrik 2022-12-27 10:45:48 UTC 
Created attachment 1934563 [details]
job invocation details
Comment 2 Jan Senkyrik 2023-03-06 14:01:54 UTC 
One more behavior that might be related:

- Choose multiple hosts (e.g. host_a, host_b, host_c, host_d) and make host_a unreachable (e.g. shutdown).
- Run All Ansible roles for these 4 hosts.

Actual result:
- All 4 hosts are shown as failed (see attached screenshot)
- Check details for host_d and you can see that all tasks finished ok but the exit code is 4:

~~~
TASK [Apply roles] *************************************************************
 165:

 166:
TASK [RedHatInsights.insights-client : Install 'insights-client'] **************
 167:
ok: [jsenkyri-rhel8-sat612-d.sysmgmt.lan]
 168:

 169:
TASK [RedHatInsights.insights-client : Set Insights Configuration Values] ******
 170:
ok: [jsenkyri-rhel8-sat612-d.sysmgmt.lan]
 171:

 172:
TASK [RedHatInsights.insights-client : Register Insights Client] ***************
 173:
ok: [jsenkyri-rhel8-sat612-d.sysmgmt.lan]
 174:

 175:
TASK [RedHatInsights.insights-client : Change permissions of Insights Config directory so that Insights System ID can be read] ***
 176:
ok: [jsenkyri-rhel8-sat612-d.sysmgmt.lan]
 177:

 178:
TASK [RedHatInsights.insights-client : Change permissions of machine_id file so that Insights System ID can be read] ***
 179:
ok: [jsenkyri-rhel8-sat612-d.sysmgmt.lan]
 180:

 181:
TASK [RedHatInsights.insights-client : Create directory for ansible custom facts] ***
 182:
ok: [jsenkyri-rhel8-sat612-d.sysmgmt.lan]
 183:

 184:
TASK [RedHatInsights.insights-client : Install custom insights fact] ***********
 185:
ok: [jsenkyri-rhel8-sat612-d.sysmgmt.lan]
 186:

 187:
TASK [RedHatInsights.insights-client : Enable Insights timer] ******************
 188:
ok: [jsenkyri-rhel8-sat612-d.sysmgmt.lan]
 189:
PLAY RECAP *********************************************************************
 190:
jsenkyri-rhel8-sat612-d.sysmgmt.lan : ok=10   changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
 191:
Exit status: 4
~~~

Expected results:
- Only host_a is shown as failed. host_b, host_c and host_d should be marked as successful.
Comment 3 Jan Senkyrik 2023-03-06 14:02:49 UTC 
Created attachment 1948364 [details]
invocation_all_failed
Comment 4 Jan Senkyrik 2023-03-06 14:10:18 UTC 
Bug 2156522 is similar but I don't think it's an exact match.
Comment 5 nalfassi 2023-05-03 15:33:54 UTC 
Created redmine issue https://projects.theforeman.org/issues/36353 from this bug
Comment 6 nalfassi 2023-11-21 11:44:02 UTC 
*** Bug 2249905 has been marked as a duplicate of this bug. ***
Comment 7 Eric Helms 2024-06-06 12:56:51 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.