Bug 2156522

Summary: Misleading job status in the new host UI when running jobs in bulk
Product: Red Hat Satellite Reporter: Jan Senkyrik <jsenkyri>
Component: HostsAssignee: Maria <magaphon>
Status: CLOSED ERRATA QA Contact: Pavel Novotny <pnovotny>
Severity: medium Docs Contact:
Priority: high    
Version: 6.12.0CC: arsingh, aruzicka, osousa, pmoravec, pnovotny, torkil
Target Milestone: 6.14.0Keywords: Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-foreman_remote_execution-10.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2191659 (view as bug list) Environment:
Last Closed: 2023-11-08 14:18:10 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
new host UI
none
job invocation none

Description Jan Senkyrik 2022-12-27 09:31:41 UTC 
Description of problem:
When a bulk REX job ends in success for host_a but fails for host_b, the new host UI page shows 'failed' for both host_a and host_b.


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

Let me explain it on a real example:
- Run a bulk REX job on 2 hosts. Search Query: name ^ (jsenkyri-rhel7, jsenkyri-rhel8)
- Job for 'jsenkyri-rhel7' was successful
- Job for 'jsenkyri-rhel8' failed
- 'Recent jobs' for 'jsenkyri-rhel7' on the new host UI page shows failed even though it was in fact successful
- See attached screenshots for better understanding: [host_page.png] [job_invocation.png]



Actual results:
Misleading job status for jsenkyri-rhel7.


Expected results:
Job for jsenkyri-rhel7 executed successfully so I'd expect the status to read 'success'.
Comment 1 Jan Senkyrik 2022-12-27 09:32:22 UTC 
Created attachment 1934558 [details]
new host UI
Comment 2 Jan Senkyrik 2022-12-27 09:33:34 UTC 
Created attachment 1934559 [details]
job invocation
Comment 4 Adam Ruzicka 2023-01-05 12:23:18 UTC 
This is valid, the new UI shows the result of the entire job, not how it went for that one particular host
Comment 10 Bryan Kearney 2023-03-17 20:02:57 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35147 has been resolved.
Comment 11 Bryan Kearney 2023-03-17 20:03:10 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35147 has been resolved.
Comment 14 Pavel Novotny 2023-10-03 14:38:06 UTC 
Verified in Satellite 6.14.0 snap 18:

rubygem-foreman_remote_execution-10.0.7-1.el8sat.noarch
satellite-6.14.0-3.el8sat.noarch

Verified by following the reproducer from comment 0.
Running a bulk remote job on two or more hosts with a mixed result, e.g., passed & failed, 
the result on the 'Recent jobs' card is reported correctly for each host.
Comment 17 errata-xmlrpc 2023-11-08 14:18:10 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