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 2156522 - Misleading job status in the new host UI when running jobs in bulk
Summary: Misleading job status in the new host UI when running jobs in bulk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.12.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: 6.14.0
Assignee: Maria
QA Contact: Pavel Novotny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-27 09:31 UTC by Jan Senkyrik
Modified: 2024-01-04 13:09 UTC (History)
6 users (show)

Fixed In Version: rubygem-foreman_remote_execution-10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2191659 (view as bug list)
Environment:
Last Closed: 2023-11-08 14:18:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
new host UI (156.14 KB, image/png)
2022-12-27 09:32 UTC, Jan Senkyrik 		no flags Details
job invocation (101.04 KB, image/png)
2022-12-27 09:33 UTC, Jan Senkyrik 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35147 0 Normal Closed Recent jobs card shows failed job when it succeeded 2023-04-27 14:04:30 UTC
Red Hat Issue Tracker SAT-14717 0 None None None 2023-01-05 15:23:09 UTC
Red Hat Issue Tracker SAT-16438 0 None None None 2023-09-13 11:14:02 UTC
Red Hat Knowledge Base (Solution) 7033199 0 None None None 2023-09-13 11:12:22 UTC
Red Hat Product Errata RHSA-2023:6818 0 None None None 2023-11-08 14:18:18 UTC

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
Note You need to log in before you can comment on or make changes to this bug.