Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1395471

Summary: [RFE] Include a Hosts reboot required indication in Satellite 6
Product: Red Hat Satellite Reporter: cpatters
Component: DashboardAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: UnspecifiedCC: avaddara, bbuckingham, bkearney, jcallaha
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-19 20:51:26 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 cpatters 2016-11-16 00:46:31 UTC
1. Proposed title of this feature request  
Include a Host reboot required indication in Satellite 6

2. Who is the customer behind the request?  
  Account: #676102 Australian Signals Directorate
  TAM customer: yes
  SRM customer: yes
  Strategic: yes

3. What is the nature and description of the request?
Satellite 5 has the feature of displaying all Systems that required a reboot and also had a reboot indication on the System's DashBoard. 

Satellite 6 currently includes a number of Hosts Health indications:
a. Green Tick;
b. Amber Exclamation Mark; and
c. Red Cross.

Request that an additional feature be added to  in Satellite 6
so to include which subscribed Hosts require a reboot and also have an indication on the Hosts Dashboard

4. Why does the customer need this?

The level of technical knowledge of personnel accessing a number of environments within the Customer base may not be aware of when Linux Systems require reboot (kernel update, system library updates). 

Also, when updating a high number of Hosts, Customer may not be fully aware of which machine require a reboot if there was a mixture of varying RHEL releases or varying functionalities of each Host.


5. How would the customer like to achieve this?
Have an indication similar to Satellite 5 that provides the user an indication that a reboot is required on 

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Customer is happy to partake in hot fixes for testing purposes.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
Bugzilla: Nil known

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
Satellite 6.4 would be a realistic release.

it is believed that this would be a feature that would also benefit other Customers as well and isn't specific to simply this Customer.

Comment 1 Bryan Kearney 2017-01-19 20:51:26 UTC

*** This bug has been marked as a duplicate of bug 1240472 ***