Bug 1297017 - hammer host reports does not return any data
Summary: hammer host reports does not return any data
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Reporting
Version: 6.1.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Martin Bacovsky
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-08 18:11 UTC by Tom Sorensen
Modified: 2020-12-11 12:02 UTC (History)
10 users (show)

Fixed In Version: rubygem-hammer_cli_foreman-0.11.0.5, foreman-1.15.6.11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:10:39 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20742 0 None None None 2017-08-25 13:04:11 UTC
Foreman Issue Tracker 21602 0 None None None 2017-11-21 10:17:21 UTC
Github theforeman/foreman/commit/820afc57b1264f72e07e4e73a14d0565d559f7f7 0 None None None 2017-11-21 10:34:04 UTC

Description Tom Sorensen 2016-01-08 18:11:37 UTC
Description of problem:
Running "hammer host reports --id XX" only outputs the column headers and not any data. Data is visible in the UI.

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

How reproducible:
Always

Steps to Reproduce:
1. Ensure that there are reports for the host in question in the UI
2. Get the id for the host by running "hammer host info --name foo | grep '^Id' | awk '{print $NF}'
3. run "hammer host reports --id XX" where XX is the id for the host from the previous command

Actual results:
Output is the column headers only, as follows:
---|------|-------------|---------|-----------|--------|------------------|--------|--------
ID | HOST | LAST REPORT | APPLIED | RESTARTED | FAILED | RESTART FAILURES | SKIPPED | PENDING
---|------|-------------|---------|-----------|--------|------------------|--------|--------


Expected results:
Data from reports screen should be displayed.

Additional info:

Comment 1 Bryan Kearney 2016-07-26 19:07:00 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 2 Bryan Kearney 2017-01-11 21:46:14 UTC
This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.

Comment 5 Tomas Strachota 2017-08-25 13:04:12 UTC
The bug isn't caused by using wrong api endpoint as http://projects.theforeman.org/issues/14510 suggests. I attached a new upstream issue and connected it with the previous one. It would be good to fix them together.

Comment 13 Satellite Program 2017-11-08 11:24:22 UTC
Upstream bug assigned to oprazak

Comment 14 Satellite Program 2017-11-08 11:24:26 UTC
Upstream bug assigned to oprazak

Comment 15 Satellite Program 2017-11-14 15:26:09 UTC
Upstream bug assigned to mbacovsk

Comment 16 Satellite Program 2017-11-14 15:26:15 UTC
Upstream bug assigned to mbacovsk

Comment 17 Satellite Program 2017-11-15 09:24:23 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20742 has been resolved.

Comment 18 Peter Ondrejka 2017-11-20 09:44:54 UTC
Checked in Sat 6.3 snap 25. Listing host reports using --name works as expected, but listing via --id returns "Error: 400 Bad Request". Will provide debug output in attachment.

Comment 20 Martin Bacovsky 2017-11-21 10:17:22 UTC
There is also related API fix that was not cherry-picked along. Adding the links

Comment 22 Evgeni Golov 2017-11-21 11:02:34 UTC
moving to needs_cherrypick for the foreman change

Comment 23 Peter Ondrejka 2017-11-27 10:02:48 UTC
Verified on Sat 6.3 snap 26, host reports can now be listed both via id and name

Comment 24 Bryan Kearney 2018-02-21 16:44:33 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, 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-2018:0336

Comment 25 Bryan Kearney 2018-02-21 17:10:39 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, 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-2018:0336


Note You need to log in before you can comment on or make changes to this bug.