Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 845096 - Some types of notifications don't go away on their own
Some types of notifications don't go away on their own
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: WebUI (Show other bugs)
6.0.1
Unspecified Unspecified
unspecified Severity unspecified (vote)
: Unspecified
: Unused
Assigned To: Brad Buckingham
Og Maciel
: TestBlocker, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-01 14:40 EDT by Og Maciel
Modified: 2013-08-16 14:04 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Success messages/notices on the dashboard behaved like warnings. They required manual closure instead of being automatic dismissal. This fix modifies the notification code and changes all success notifications to not remain permanently on the dashboard.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-12-04 14:50:04 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-04 19:39:57 EST

  None (edit)
Description Og Maciel 2012-08-01 14:40:57 EDT
Description of problem:

I noticed that sometimes successful notifications will "stick" to the dashboard and won't go away on their own. This may be reproduced by running promotions.

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


How reproducible:


Steps to Reproduce:
1. promote an existing repo
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Mike McCune 2012-08-07 12:09:32 EDT
The only thing that should stay on the screen are errors and warnings.  everything else should fade out
Comment 2 Jeff Weiss 2012-08-08 15:05:34 EDT
The real issue here is not about the fading.  The problem is that a notification containing a successful message was displayed as gray "message" type, when it should be a green "success" type.

The promotion success message is now gray, it was (and should be) green.
Comment 3 Brad Buckingham 2012-08-23 09:42:43 EDT
Prior to the bz there was some refactoring done on notices.  When that happened the promotions 'success' notice was incorrectly updated to be a 'message' notice (i.e. notify.message / Notify.message).  The 'message' class will create a notice that when displayed has a grayish background and is 'sticky', requiring the user to manually close it.

From a scan of the code (i.e. [n|N]otify.message), the only usages of the 'message' class were:
1. notice created after successful promotion
2. notice created when a newly created object no longer meets current search criteria for the page
3. notice created when a user's default environment has been removed and user is informed to select another one

1, should be defined as a success.
2 & 3 were intentionally defined as 'message' because they are not errors, but the user should be aware.

The following katello commit addresses the issue of the promotion notice:
https://github.com/Katello/katello/commit/ea18172fbbb7c993e35f12a8b5a5b7f0f1c7cd81
Comment 5 Og Maciel 2012-09-17 19:40:14 EDT
Verified using:

* candlepin-0.7.8-1.el6cf.noarch
* candlepin-selinux-0.7.8-1.el6cf.noarch
* candlepin-tomcat6-0.7.8-1.el6cf.noarch
* katello-1.1.12-7.el6cf.noarch
* katello-all-1.1.12-7.el6cf.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.1.8-1.el6cf.noarch
* katello-cli-1.1.8-4.el6cf.noarch
* katello-cli-common-1.1.8-4.el6cf.noarch
* katello-common-1.1.12-7.el6cf.noarch
* katello-configure-1.1.9-3.el6cf.noarch
* katello-glue-candlepin-1.1.12-7.el6cf.noarch
* katello-glue-pulp-1.1.12-7.el6cf.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-1.1.1-1.el6cf.noarch
* pulp-1.1.12-1.el6cf.noarch
* pulp-common-1.1.12-1.el6cf.noarch
* pulp-selinux-server-1.1.12-1.el6cf.noarch
Comment 7 errata-xmlrpc 2012-12-04 14:50:04 EST
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.

http://rhn.redhat.com/errata/RHSA-2012-1543.html
Comment 8 Mike McCune 2013-08-16 14:04:00 EDT
getting rid of 6.0.0 version since that doesn't exist

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