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.
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
> 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
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