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.
Bug 1467491 - [RFE] [6.3] The content on dashboard items must be updated
Summary: [RFE] [6.3] The content on dashboard items must be updated
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Managing Hosts
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Michaela Slaninkova
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-04 03:45 UTC by Andrew Dahms
Modified: 2019-09-26 18:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-12 11:27:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Andrew Dahms 2017-07-04 03:45:50 UTC 
"Chapter 1. Using the Red Hat Satellite Content Dashboard" in the Host Configuration Guide is out of date, and must be updated to include the currently available items.

Major changes include the following -

* 'Content Host Subscription Status' should be changed to 'Host Subscription
  Status', and the status types checked.

* A similar table for 'Host Configuration Status' should be added.

* A similar table for 'Virt-who Configuration Status' should be added.

* Other items, such as for 'Red Hat Insights Actions' and 'Red Hat Insights Risk
  Summary', should be described.
Comment 1 Andrew Dahms 2017-07-05 06:23:49 UTC 
Assigning to Misha for review.
Comment 3 Andrew Dahms 2017-07-05 23:31:25 UTC 
Hi Misha,

Thank you for your needinfo request.

In response to your questions -

* Host Configuration Status

  A little more detail would be useful, even if we just change the simple
  explanations we currently have into full sentences. For example, 'Hosts in
  error state' to 'Hosts on which an error was detected during the last
  reporting interval'.

* Virt-who Configuration Status

  After searching for 'Virt-who Configuration Status', I found the following
  link -

  projects.theforeman.org/issues/19330

  This provides a few more details about what each of these items used to be, 
  although there have been some other changes as well by the looks of it.
  Based on this, it looks like each item explains the status of reports
  received from the virt-who daemon running on hosts in the environment. These
  look similar to those for hosts - no reports received, no changes applied,
  no changes needed so everything is unchanged and thus ok, and the total.

* Red Hat Insights Actions, Red Hat Insights Risk Summary

  Red Hat Insights is a tool embedded in Satellite and other products that
  checks the environment and suggests actions you can take. For the first item,
  a simple explanation of the 'type' of actions, such as 'Stability' might be
  useful. Unfortunately, I cannot find a detailed explanation as yet, so
  just a simple explanation will have to do for now. Rather than having a 
  full table, maybe just a quick paragraph explaining that issues are sorted
  into categories will do. The same for the risk levels in the second item.

Let me know if you have any further questions.

Kind regards,

Andrew
Comment 9 Michaela Slaninkova 2017-07-12 11:27:04 UTC 
Hello,


This BZ ticket has been resolved and I am closing it as next release.
Comment 10 Andrew Dahms 2018-01-15 01:18:40 UTC 
Updating the component and doc type.
Note You need to log in before you can comment on or make changes to this bug.