Hide Forgot
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:
Moving 6.2 bugs out to sat-backlog.
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.
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.
Upstream bug assigned to oprazak
Upstream bug assigned to mbacovsk
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20742 has been resolved.
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.
There is also related API fix that was not cherry-picked along. Adding the links
moving to needs_cherrypick for the foreman change
Verified on Sat 6.3 snap 26, host reports can now be listed both via id and name
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