Bug 1825458

Summary: Showing a Job Invocation should have an option to list outcome on individual Hosts
Product: Red Hat Satellite Reporter: Pavel Moravec <pmoravec>
Component: Remote ExecutionAssignee: Leos Stejskal <lstejska>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.6.0CC: aruzicka, inecas, lstejska, nshaik, zhunting
Target Milestone: 6.9.0Keywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: tfm-rubygem-hammer_cli_foreman_remote_execution-0.2.1, tfm-rubygem-foreman_remote_execution-3.3.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-21 13:14:53 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:

Description Pavel Moravec 2020-04-18 09:01:22 UTC 
Description of problem:
When querying for details of a Job Invocation, WebUI shows list of individual Hosts and job statuses. While this is not offered by API or hammer:

GET /api/job_invocations/:id (as well as hammer) just prints summary stats and list of Hosts the job was run on. Not statuses from the hosts. So a CLI approach to get e.g. a list of Hosts, that failed the job, must iterate via:

GET /api/job_invocations/:id/hosts/:host_id

for all hosts. That is user-unfriendly.

Please, extend API request "GET /api/job_invocations/:id" (and also hammer) by an option to get statuses of job execution on individual Hosts.


Version-Release number of selected component (if applicable):
Sat 6.6


How reproducible:
100%


Steps to Reproduce:
1. Invoke a job against multiple Hosts.
2. Once the job completes, try to get via API or hammer list of hosts+statuses of the Job Invocation.


Actual results:
2. No one call for this, one has to iterate over individual job+host details.


Expected results:
2. An option in the request and also in hammer for this.


Additional info:
Inspired by https://access.redhat.com/discussions/4968991
Comment 3 Leos Stejskal 2020-05-18 11:23:42 UTC 
Created redmine issue https://projects.theforeman.org/issues/29867 from this bug
Comment 4 Bryan Kearney 2020-06-23 12:01:38 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/29867 has been resolved.
Comment 5 Adam Ruzicka 2020-06-23 13:49:39 UTC 
Hammer part is still not merged, moving back to assigned
Comment 6 Bryan Kearney 2020-06-23 16:01:20 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/29867 has been resolved.
Comment 8 Leos Stejskal 2020-11-24 06:19:27 UTC 
> Why not show it in info by default?
The reason is performance. Showing job status for hundreds of hosts can take several minutes. So far there isn't any easy fix for it.

> let's make it behave like a flag
Hmm, I'll look into it, this is how it suppose to behave (at least what I remember and what I see in PR description). Anyway you are right, it should be a flag
Comment 9 Peter Ondrejka 2020-12-10 13:05:18 UTC 
Verified on Satellite 6.9 snap 5, the --show-host-status flag is in place and behaves as expected
Comment 14 errata-xmlrpc 2021-04-21 13:14:53 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 (Moderate: Satellite 6.9 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-2021:1313