Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1687852 - [RFE] Need to have host sub status to identify that insights is enabled on registered client [NEEDINFO]
Summary: [RFE] Need to have host sub status to identify that insights is enabled on re...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: rubygem-foreman-redhat_access
Version: 6.4.0
Hardware: x86_64
OS: Linux
urgent
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-12 13:38 UTC by Mahesh Yadav
Modified: 2019-04-09 03:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
rjerrido: needinfo? (rjerrido)


Attachments (Terms of Use)

Description Mahesh Yadav 2019-03-12 13:38:42 UTC
Description of problem:

Need to have a notification for clients on Red Hat Satellite Web UI, whether insights is enabled on the registered client or not.
Just like we see katello-agent in host details.


Version-Release number of selected component (if applicable):
Satellite 6.4.0 and above


How reproducible:
Need to implement this feature in Satellite Web UI in clients details summary tab.
If the insights is enabled just showing the green notification.
If not it should show red.  Similar to Katello-agent.


Additional info:
The ability to look at the current RHEL fleet from the Satellite dashboard and see if insights is enabled on this particular RHEL system or not.

Comment 3 Marek Hulan 2019-03-12 15:42:45 UTC
So this is not in fact notification in notification drawer, but rather host sub status - similar to katello agent. Moving to proper component.


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