Bug 1994679
Summary: | Host - Last Checkin report template is not showing any other content host apart from Red Hat Satellite itself. | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Kshitij <kupadhya> |
Component: | Reporting | Assignee: | Marek Hulan <mhulan> |
Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.10.0 | CC: | ahumbe, lvrtelov, mhulan, pcreech, saydas, smallamp, zhunting |
Target Milestone: | 6.11.0 | Keywords: | Triaged, UserExperience |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rubygem-foreman-3.1.1.17 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-07-05 14:29:34 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
Kshitij
2021-08-17 16:46:33 UTC
Based on the above comments, this is NOT a regression - correct?? Created redmine issue https://projects.theforeman.org/issues/34809 from this bug Upstream bug assigned to mhulan Upstream bug assigned to mhulan Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34809 has been resolved. Verified with Sat 6.11 snap 22.0. Report template's description now reads: ``` This report lists hosts that haven't checked in in the specified interval (by default 5 hours). By default it also includes hosts we don't have last check information for. The check in is based on the subscription manager communication. ``` I think this describes the functionality of the report very well. Note that in comment 4, Marek states `I think we should add a description to every report and display that in the UI when rendering`. None of that happened but I think it's out of the scope of this BZ. 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.11 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-2022:5498 |