Bug 803548 - Async success notifications pop up from syncs in other orgs
Summary: Async success notifications pop up from syncs in other orgs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: Unspecified
Assignee: Petr Chalupa
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-15 01:32 UTC by Jeff Weiss
Modified: 2019-09-26 15:54 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Organization specific changes appeared out of context in the notification messages, making it hard to reference which changes were done for which organization. Notifications now refer to the appropriate organization for specific actions or changes.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:42:50 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1543 0 normal SHIPPED_LIVE Important: CloudForms System Engine 1.1 update 2012-12-05 00:39:57 UTC

Description Jeff Weiss 2012-03-15 01:32:37 UTC
Description of problem:


Version-Release number of selected component (if applicable):
Katello Version: 0.2.13-1.git.3.bd54a84.el6

How reproducible:
always

Steps to Reproduce:
1. As admin, create an org "myorg", switch to it
2. Create a custom provider/prod/repo (repo large enough to take more than a few seconds to sync)
3. Start the sync of the repo, immediately switch to ACME_Corporation org
4. wait (long enough for the sync to complete - might need to query pulp to find out when it's done)
5. reload the page
  
Actual results:
get an async notification about the successful sync of your repo

Expected results:
No notification 

Additional info:
What's even more bizarre is, if you sync several repos at once, you will eventually get success notifications for all of them.  But one at a time.  Each new page load will show one new notification.

I think these notifications should be removed completely.

Comment 1 Petr Chalupa 2012-09-06 09:34:15 UTC
fixed in a6846e21a1ad3ff8667d7d18981206e487ac82ed

Comment 3 Og Maciel 2012-09-18 00:07:09 UTC
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 5 errata-xmlrpc 2012-12-04 19:42:50 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.

http://rhn.redhat.com/errata/RHSA-2012-1543.html


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