Project

General

Profile

Actions

Bug #29867

closed

Showing a Job Invocation should have an option to list outcome on individual Hosts

Added by Leos Stejskal almost 4 years ago. Updated over 3 years ago.


Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1825458

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

Actions #1

Updated by The Foreman Bot almost 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/494 added
Actions #2

Updated by The Foreman Bot almost 4 years ago

  • Pull request https://github.com/theforeman/hammer_cli_foreman_remote_execution/pull/32 added
Actions #3

Updated by The Foreman Bot almost 4 years ago

  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/495 added
Actions #4

Updated by Leos Stejskal almost 4 years ago

  • Assignee set to Leos Stejskal
Actions #5

Updated by The Foreman Bot almost 4 years ago

  • Fixed in Releases foreman_remote_execution 3.3.2 added
Actions #6

Updated by Leos Stejskal almost 4 years ago

  • Status changed from Ready For Testing to Closed
Actions #7

Updated by The Foreman Bot almost 4 years ago

  • Fixed in Releases hammer_cli_foreman_remote_execution 0.1.2 added
Actions #8

Updated by Adam Ruzicka over 3 years ago

  • Fixed in Releases hammer_cli_foreman_remote_execution 0.2.0 added
  • Fixed in Releases deleted (hammer_cli_foreman_remote_execution 0.1.2)
Actions #9

Updated by Adam Ruzicka over 3 years ago

  • Pull request deleted (https://github.com/theforeman/foreman_remote_execution/pull/495)
Actions #10

Updated by The Foreman Bot over 3 years ago

  • Pull request https://github.com/theforeman/hammer_cli_foreman_remote_execution/pull/38 added
Actions #11

Updated by Adam Ruzicka over 3 years ago

  • Fixed in Releases hammer_cli_foreman_remote_execution 0.2.1 added
  • Fixed in Releases deleted (foreman_remote_execution 3.3.2, hammer_cli_foreman_remote_execution 0.2.0)
Actions

Also available in: Atom PDF