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 1488998 - Notification not cleared when there is not discovered host
Summary: Notification not cleared when there is not discovered host
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Dashboard
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Sebastian Gräßl
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-06 14:55 UTC by Renzo Nuccitelli
Modified: 2019-04-01 20:26 UTC (History)
7 users (show)

Fixed In Version: foreman-1.15.6.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:29:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Notification with no discovery host (40.80 KB, image/png)
2017-09-06 14:57 UTC, Renzo Nuccitelli 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21026 0 None None None 2017-09-20 04:04:43 UTC

Description Renzo Nuccitelli 2017-09-06 14:55:21 UTC 
Description of problem:

No notification regarding Discovery Host should be visible when there is no one available (see screenshot).

Version-Release number of selected component (if applicable):

Satellite 6.3 snap 14

How reproducible:

Always


Steps to Reproduce:
1. Create a Discovery Host
2. Delete the Discovery Host

Actual results:

There is a notifications regarding discovery host even in its absence. 

Expected results:

No notifications regarding discovery host.


Additional info:
Comment 1 Renzo Nuccitelli 2017-09-06 14:57:43 UTC 
Created attachment 1322695 [details]
Notification with no discovery host
Comment 4 Sebastian Gräßl 2017-09-20 04:04:35 UTC 
Created redmine issue http://projects.theforeman.org/issues/21026 from this bug
Comment 5 Satellite Program 2017-09-20 06:10:30 UTC 
Upstream bug assigned to sgraessl
Comment 6 Satellite Program 2017-10-25 10:15:19 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21026 has been resolved.
Comment 8 Nikhil Kathole 2017-11-23 12:18:42 UTC 
VERIFIED

Version Tested:
Satellite-6.3 Snap 25

steps:
 
scenario 1:
1. Discovered a host
2. Deleted host
Found Notification cleared.

scenario 2:
1. Discovered two hosts
2. Deleted one host
Notification was present
3. Deleted second host
Found no Notification.

scenario 3:
1. Discovered a host
2. Read notification (clicked on notification)
3. Deleted discovered host
4. Clicked on notification box 
Found notification cleared.

scenario 4:
1. Discovered host
2. provisioned host
Found notification cleared.
Comment 9 Bryan Kearney 2018-02-21 17:29:26 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.