Bug 2167396 - job invocation shows wrong info after remote execution job (regression from 6.11)
Summary: job invocation shows wrong info after remote execution job (regression from 6...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible - Configuration Management
Version: 6.12.1
Hardware: x86_64
OS: All
unspecified
high
Target Milestone: 6.14.0
Assignee: nalfassi
QA Contact: addubey
Zuzana Lena Ansorgova
URL:
Whiteboard:
: 2136531 2167532 2168597 2172118 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-06 14:17 UTC by Oliver Ilian
Modified: 2023-11-08 14:19 UTC (History)
19 users (show)

Fixed In Version: rubygem-smart_proxy_ansible-3.5.4
Doc Type: Known Issue
Doc Text:
.Job invocation details show incorrect results of execution on multiple hosts When you run an Ansible job against multiple hosts and the execution fails on some hosts, the results of the execution on all hosts are marked as failed in the job invocation details. As a result, partial failure of jobs is not respected and you can see the failed result status even for hosts on which execution succeeded. This is fixed in the 6.13.1 update.
Clone Of:
: 2184117 2190464 (view as bug list)
Environment:
Last Closed: 2023-11-08 14:18:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36130 0 Normal Closed job invocation shows wrong info after remote execution job (regression from 6.11) 2023-03-27 12:04:17 UTC
Red Hat Issue Tracker SAT-15789 0 None None None 2023-02-09 15:55:20 UTC
Red Hat Issue Tracker SAT-16045 0 None None None 2023-05-11 09:33:10 UTC
Red Hat Knowledge Base (Solution) 7009151 0 None None None 2023-04-24 12:14:37 UTC
Red Hat Product Errata RHSA-2023:6818 0 None None None 2023-11-08 14:19:06 UTC

Description Oliver Ilian 2023-02-06 14:17:17 UTC 
Description of problem:
A customer reported, that after they migrated to Satellite 6.12 (from 6.11) the job invocation overview is showing the wrong info. After running an ansible remote execution job on several hosts, if one host failed, all hosts are shown as failed.

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

How reproducible:
always

Steps to Reproduce:
1. Prepare to run any ansible job in Satellite 6.12.1 and run it on a group of hosts 
2. Force the job to fail on one host (for example with a wrong DNF repository, which causes this one host to fail "really")
3. Start the job
4. Ansible-runner returns error code 2 (partial failure) instead of 0 and this causes Satellite to mark every host in this job run as failed -> not just the one, which really failed

Actual results:
All hosts are shown as failed when only one has failed

Expected results:
Show correct info about remote execution on hosts (failed / successful)

Additional info:
The customer is relying on this info for patching but does not get the right info currently. This seems to be a regression from Satellite 6.11.
Comment 1 Adam Ruzicka 2023-02-06 14:50:13 UTC 
This belongs to ansible. Remote execution only displays data it gets from ansible (smart_proxy_ansible to be precise)
Comment 2 Adam Ruzicka 2023-02-07 08:14:52 UTC 
*** Bug 2167532 has been marked as a duplicate of this bug. ***
Comment 3 nalfassi 2023-02-20 14:52:12 UTC 
Created redmine issue https://projects.theforeman.org/issues/36130 from this bug
Comment 4 nalfassi 2023-02-28 13:01:47 UTC 
*** Bug 2172118 has been marked as a duplicate of this bug. ***
Comment 6 nalfassi 2023-03-05 13:49:42 UTC 
*** Bug 2168597 has been marked as a duplicate of this bug. ***
Comment 7 Bryan Kearney 2023-03-07 16:03:22 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36130 has been resolved.
Comment 10 Bryan Kearney 2023-03-16 16:03:41 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36130 has been resolved.
Comment 11 Bryan Kearney 2023-03-16 16:03:48 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36130 has been resolved.
Comment 12 nalfassi 2023-03-20 09:50:45 UTC 
*** Bug 2136531 has been marked as a duplicate of this bug. ***
Comment 24 errata-xmlrpc 2023-11-08 14:18:30 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.14 security and bug fix update), 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-2023:6818
Note You need to log in before you can comment on or make changes to this bug.